X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8FE0DD9D0E for ; Fri, 7 Oct 2005 17:13:51 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 88833-03 for ; Fri, 7 Oct 2005 20:13:48 +0000 (GMT) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.204]) by svr1.postgresql.org (Postfix) with ESMTP id 72C51D83C7 for ; Fri, 7 Oct 2005 17:13:48 -0300 (ADT) Received: by xproxy.gmail.com with SMTP id s14so531271wxc for ; Fri, 07 Oct 2005 13:13:51 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=ZJ6ux+Z7hHApQvX5qNP63ULdzHaV63uQjt1PqpTrW98GsnMgOtcI2AOaTy7A4z/eFjVhrq6UjoYYAgyLzr7wMAvLnRrLECmsblF1Y8hRI2Kd9GlkqwQy1S0odN7ht6gHTULmZxjjGlWebpZlaB1lAHWKyGQYpQnNFQQrFj/puTc= Received: by 10.70.13.4 with SMTP id 4mr2741538wxm; Fri, 07 Oct 2005 13:13:50 -0700 (PDT) Received: by 10.70.87.15 with HTTP; Fri, 7 Oct 2005 13:13:50 -0700 (PDT) Message-ID: <1d219a6f0510071313h3aa2c7c6x10bc33d6a7740c3b@mail.gmail.com> Date: Fri, 7 Oct 2005 16:13:50 -0400 From: Chris Hoover Reply-To: Chris Hoover To: pgsql-admin@postgresql.org Subject: How to check for pg_dump errors? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1263_27884129.1128716030762" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.437 required=5 tests=[AWL=0.274, HTML_00_10=0.138, HTML_MESSAGE=0.001, RCVD_BY_IP=0.024] X-Spam-Level: X-Archive-Number: 200510/93 X-Sequence-Number: 19165 ------=_Part_1263_27884129.1128716030762 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Silly question, but in a shell script, what is the best way to check for a pg_dump problem? I'm working on reworking our backup methodology, and want to make sure that if pg_dump can't dump a db, we page the on call db. Does it return any sort of exit code indicating it was not successful dumping a database? Thanks, Chris ------=_Part_1263_27884129.1128716030762 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Silly question, but in a shell script, what is the best way to check for a pg_dump problem?  I'm working on reworking our backup methodology, and want to make sure that if pg_dump can't dump a db, we page the on call db.  Does it return any sort of exit code indicating it was not successful dumping a database?

Thanks,

Chris
------=_Part_1263_27884129.1128716030762--