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 200712112348.20879.peter_e@gmx.net
Whole thread Raw
In response to Re: archive_command failures report confusing exit status  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: archive_command failures report confusing exit status  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> No, you are confusing the cases "called shell was killed by a signal"
> and "called command was killed by a signal, which the shell then turned
> around and reported to us as exit > 128".

Yes, I had missed that difference.  Next try ...

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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: printQuery API change proposal (was Re: psql \dFp's behavior)
Next
From: Simon Riggs
Date:
Subject: Re: WORM and Read Only Tables (v0.1)