Re: archive_command failures report confusing exit status

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: archive_command failures report confusing exit status
Date: 2007-12-10 18:36:02
Message-ID: 20071210183602.GB27126@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

(Hmm, there is nearly duplicate code in pclose_check already).

--
Alvaro Herrera http://www.amazon.com/gp/registry/DXLWNGRJD34J
"Nunca confiaré en un traidor. Ni siquiera si el traidor lo he creado yo"
(Barón Vladimir Harkonnen)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikolay Grebnev 2007-12-10 18:36:03 Trigger proglem
Previous Message Peter Eisentraut 2007-12-10 18:25:53 Re: Problem of a server gettext message.