Re: recovery.conf location - Mailing list pgsql-hackers

From Robert Haas
Subject Re: recovery.conf location
Date
Msg-id AANLkTim3SPYZz_QzL52Gv8Ah1VNA2rwabp_cxnd+st38@mail.gmail.com
Whole thread Raw
In response to Re: recovery.conf location  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Wed, Sep 29, 2010 at 3:14 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> On Tue, Sep 28, 2010 at 10:34 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> The idea of relying on the existence of recovery.conf to determine
>> whether we should continue recovery forever or switch to normal
>> running seems somewhat klunky to me.  It mixes up settings with
>> control information.  Maybe the control information should move to
>> pg_control, and the settings to postgresql.conf.  *waves hands*
>
> You mean to move standby_mode to postgresql.conf, and determine
> whether the server should start in standby mode or not by considering
> of standby_mode and the status information in pg_control?

I can't parse that.  I guess I'm wondering whether standby_mode itself
should move into pg_control.  Otherwise, you need a GUC somewhere that
says whether or not you should even try standby_mode plus a trigger
file that can override the GUC.  It seems like there's one bit of
information that's being spread out across multiple places.

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: security hook on table creation
Next
From: Josh Kupershmidt
Date:
Subject: Re: ask for review of MERGE