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 4EF5DDA543 for ; Fri, 7 Oct 2005 17:50:00 -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 03677-01 for ; Fri, 7 Oct 2005 20:49:57 +0000 (GMT) Received: from gauss.credativ.com (ipx11302.ipxserver.de [212.112.227.254]) by svr1.postgresql.org (Postfix) with ESMTP id 3A36BDA506 for ; Fri, 7 Oct 2005 17:49:57 -0300 (ADT) Received: from [192.168.0.100] (p5089AF4A.dip0.t-ipconnect.de [80.137.175.74]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by gauss.credativ.com (Postfix) with ESMTP id F36E8D7656; Fri, 7 Oct 2005 22:49:54 +0200 (CEST) From: Peter Eisentraut To: Chris Hoover Subject: Re: How to check for pg_dump errors? Date: Fri, 7 Oct 2005 22:49:46 +0200 User-Agent: KMail/1.8.1 References: <1d219a6f0510071313h3aa2c7c6x10bc33d6a7740c3b@mail.gmail.com> In-Reply-To: <1d219a6f0510071313h3aa2c7c6x10bc33d6a7740c3b@mail.gmail.com> Cc: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510072249.47043.peter_e@gmx.net> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.055 required=5 tests=[AWL=0.005, FORGED_RCVD_HELO=0.05] X-Spam-Level: X-Archive-Number: 200510/95 X-Sequence-Number: 19167 Am Freitag, 7. Oktober 2005 22:13 schrieb Chris Hoover: > Silly question, but in a shell script, what is the best way to check for a > pg_dump problem? 0 is success, nonzero is failure.