From: | Erik Jones <erik(at)myemma(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump warning format? |
Date: | 2007-03-16 14:25:55 |
Message-ID: | 3F47464F-7CCC-4278-970C-5E10621F79EB@myemma.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mar 15, 2007, at 9:08 PM, Tom Lane wrote:
> Erik Jones <erik(at)myemma(dot)com> writes:
>> Basically I need a way for my script to know if it needs to
>> abort because there were issues with the dump before it follows
>> through with the drop db...
>
> Well, just checking the exit status from pg_dump ought to give you at
> least a go/no-go indicator. If you want to be significantly more
> paranoid, you could try the theory that *any* output to stderr is
> indicative of a problem.
Thanks. I guess I just wasn't sure as to whether or not anything
other than "bad" messages were written to stderr. Given the intent
of stderr you wouldn't think so, but I've seen cases where it was so.
erik jones <erik(at)myemma(dot)com>
sofware developer
615-296-0838
emma(r)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-03-16 14:44:32 | Re: simple coordinate system |
Previous Message | Joshua D. Drake | 2007-03-16 14:22:11 | Re: Practical question. |