Re: archive_command failures report confusing exit status

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: archive_command failures report confusing exit status
Date: 2007-12-11 22:48:20
Message-ID: 200712112348.20879.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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/

Attachment Content-Type Size
log-archive-command-exitstatus.patch text/x-diff 1.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2007-12-11 23:00:30 Re: WORM and Read Only Tables (v0.1)
Previous Message Tom Lane 2007-12-11 22:42:35 printQuery API change proposal (was Re: psql \dFp's behavior)