From: Tom Lane <tgl@sss.pgh.pa.us>
To: Chris Hoover <revoohc@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: How to check for pg_dump errors?
Date: Fri, 07 Oct 2005 16:33:00 -0400
Message-ID: <8109.1128717180@sss.pgh.pa.us> (raw)
In-Reply-To: <1d219a6f0510071313h3aa2c7c6x10bc33d6a7740c3b@mail.gmail.com>
References: <1d219a6f0510071313h3aa2c7c6x10bc33d6a7740c3b@mail.gmail.com>
Chris Hoover <revoohc@gmail.com> writes:
> 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?
pg_dump should return nonzero exit code on failure. (At least in recent
releases ... not sure about how far back that's been done consistently.)
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, revoohc@gmail.com
Subject: Re: How to check for pg_dump errors?
In-Reply-To: <8109.1128717180@sss.pgh.pa.us>
References: <1d219a6f0510071313h3aa2c7c6x10bc33d6a7740c3b@mail.gmail.com> <8109.1128717180@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox