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

From Fujii Masao
Subject Re: Stefan's bug (was: max_standby_delay considered harmful)
Date
Msg-id AANLkTilRr_aPBKYEUX9geDLxHKjEs_WlOjbuadDxTBkF@mail.gmail.com
Whole thread Raw
In response to Re: Stefan's bug (was: max_standby_delay considered harmful)  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Stefan's bug (was: max_standby_delay considered harmful)
List pgsql-hackers
On Wed, May 19, 2010 at 2:47 PM, Fujii Masao <masao.fujii@gmail.com> wrote:
>>> Oh, right. How about allowing the postmaster only in PM_STARTUP,
>>> PM_RECOVERY, PM_HOT_STANDBY or PM_WAIT_READONLY state to invoke
>>> walreceiver? We can keep walreceiver alive until all read only
>>> backends have gone, and prevent unexpected startup of walreceiver.
>>
>> Yes, that seems like something we should be checking, if we aren't already.
>
> I'll do that.

Here is the updated version. I added the above-mentioned check
into the patch.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Attachment

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Specification for Trusted PLs?
Next
From: KaiGai Kohei
Date:
Subject: Re: ExecutorCheckPerms() hook