Re: recovery consistent != hot standby - Mailing list pgsql-hackers

From Robert Haas
Subject Re: recovery consistent != hot standby
Date
Msg-id AANLkTinPQJM4JY97CbRaS0CUJxf7Gab8In09FZNOo5d4@mail.gmail.com
Whole thread Raw
In response to Re: recovery consistent != hot standby  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, May 14, 2010 at 5:23 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> PM_RECOVERY_CONSISTENT -> PM_HOT_STANDBY
>> PMSIGNAL_RECOVERY_CONSISTENT -> PMSIGNAL_BEGIN_HOT_STANDBY
>
> +1.  From the point of view of the postmaster, whether the state
> transition happens immediately upon reaching consistency, or at a
> later time, or perhaps even earlier (if we could make that work)
> is not relevant.  What's relevant is that it's allowed to let in
> hot-standby backends.  So the current naming overspecifies the
> meaning of the state and the transition event.

Done.

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


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Keepalive for max_standby_delay
Next
From: Heikki Linnakangas
Date:
Subject: Re: Keepalive for max_standby_delay