Re: Stefan's bug (was: max_standby_delay considered harmful) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Stefan's bug (was: max_standby_delay considered harmful)
Date
Msg-id 18461.1274271689@sss.pgh.pa.us
Whole thread Raw
In response to Re: Stefan's bug (was: max_standby_delay considered harmful)  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Stefan's bug (was: max_standby_delay considered harmful)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, May 19, 2010 at 1:47 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
>> Yes, but I prefer XLogCtl->SharedRecoveryInProgress, which is the almost
>> same indicator as the boolean you suggested. Thought?

> It feels cleaner and simpler to me to use the information that the
> postmaster already collects rather than having it take locks and check
> shared memory, but I might be wrong.  Why do you prefer doing it that
> way?

The postmaster must absolutely not take locks (once there are competing
processes).  This is non negotiable from a system robustness standpoint.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: BYTEA / DBD::Pg change in 9.0 beta
Next
From: Simon Riggs
Date:
Subject: Re: Stefan's bug (was: max_standby_delay considered harmful)