Re: comment needs to be updated for HS?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: comment needs to be updated for HS?
Date: 2010-05-13 02:56:28
Message-ID: AANLkTikl9ljg7ujYXEttjLBaaVsTFQk6kWdY6xnaQXav@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 12, 2010 at 9:59 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Thu, May 13, 2010 at 4:20 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> postmaster.c contains the following comment just above the definition
>> of PMState.  It appears to be out of date:
>>
>>  * After reaching a consistent point in WAL redo, startup process signals
>>  * us again, and we switch to PM_RECOVERY_CONSISTENT state. There's currently
>>  * no difference between PM_RECOVERY and PM_RECOVERY_CONSISTENT, but we
>>  * could start accepting connections to perform read-only queries at this
>>  * point, if we had the infrastructure to do that.
>
> But the first sentence of the above seems to be correct and helpful. No?

Yes. I was just quoting the whole thing for context.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2010-05-13 03:07:06 Re: recovery getting interrupted is not so unusual as it used to be
Previous Message Fujii Masao 2010-05-13 02:46:44 Re: max_standby_delay considered harmful