Re: archive_command failures report confusing exit status - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: archive_command failures report confusing exit status
Date
Msg-id 200712111727.39553.peter_e@gmx.net
Whole thread Raw
In response to Re: archive_command failures report confusing exit status  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: archive_command failures report confusing exit status  (Simon Riggs <simon@2ndquadrant.com>)
Re: archive_command failures report confusing exit status  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Am Montag, 10. Dezember 2007 schrieb Alvaro Herrera:
> Peter Eisentraut wrote:
> > I figured it would make sense if pgarch.c used the same mechanism that
> > postmaster.c uses to report the various variants of regular and signal
> > exits.
>
> Hmm.  Getting rid of the "(PID 0)" is going to be a mess enough for
> translations that I think it is worth pgarch.c having its own routine
> for this.  Furthermore I think the detailed archive command should be
> reported in an errdetail() field, which makes it even farther off.

Better patch.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUGS] BUG #3799: csvlog skips some logs
Next
From: Tom Lane
Date:
Subject: Re: PGparam proposal