From: | "Damian C" <jamianb(at)gmail(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: pg_dump output goes to stderr, not stdout?!? |
Date: | 2006-08-21 01:34:07 |
Message-ID: | 2bbc8f530608201834r43cd9012wdcff5146d262f6ec@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Tom,
Very clear and dare I say obvious!!
I do check the process exit code already, so I'll ignore stderr and
stdout commentary, and use the exit code to track success, or reasons
for failure.
Many thanks,
-Damian.
On 8/21/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Damian C" <jamianb(at)gmail(dot)com> writes:
> > QuestionOne: Should this output go to sdout, and NOT to stderr???
>
> No, because what normally goes to stdout is the dump data proper.
> Commentary has to be sent to stderr to keep it separate.
>
> As a general rule I don't think programs should have to read other
> programs' stderr output at all --- certainly not for "did it work or
> not" questions. What you ought to be doing is looking at pg_dump's
> process exit code to find out whether it had a problem or not.
>
> As for whether it's worth logging the stderr output for human
> inspection: probably, but don't use -v. -v is *intended* to
> create a lot of normally-useless chatter.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | ben sewell | 2006-08-21 09:38:01 | Postgresq 8,1 hangs when running function |
Previous Message | Tom Lane | 2006-08-21 01:23:36 | Re: pg_dump output goes to stderr, not stdout?!? |