Re: unable to fail over to warm standby server - Mailing list pgsql-bugs

From Tom Lane
Subject Re: unable to fail over to warm standby server
Date
Msg-id 24571.1265752772@sss.pgh.pa.us
Whole thread Raw
In response to Re: unable to fail over to warm standby server  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-bugs
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Tom Lane wrote:
>> Yes.  Please see the existing code in the postmaster that prints
>> subprocess exit codes, and duplicate it (or perhaps refactor so you can
>> avoid code duplication; though translatability of messages might limit
>> what you can do there).

> Here's what I came up with. Translatability indeed makes it pretty hard,
> I ended up copy-pasting.

Looks reasonable to me.  One possible objection is that someone running
in "terse" logging mode would not get any information about the child
process's exit code, since errdetail would be suppressed in that case.
But we can probably live with that --- as far as I can tell, few people
use terse-mode logging.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: unable to fail over to warm standby server
Next
From: Alvaro Herrera
Date:
Subject: Re: unable to fail over to warm standby server