Re: [COMMITTERS] pgsql: Allow external recovery_config_directory

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Allow external recovery_config_directory
Date: 2013-03-27 18:15:02
Message-ID: CAHGQGwEQH8T+8jWt947pqpD70Tdr_pHA=VPNkrNG9TedbNkuoQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Thu, Mar 28, 2013 at 1:24 AM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> On 27.03.2013 18:10, Simon Riggs wrote:
>>
>> On 27 March 2013 15:35, Heikki Linnakangas<hlinnakangas(at)vmware(dot)com>
>> wrote:
>>>
>>> Ok, cool. Can you please revert this commit so that we can move on, then?
>>
>>
>> Please explain why you want this reverted, without mentioning the
>> other task we agree is required.
>
>
> If an admin can't trust that the file is placed in $PGDATA, it's harder to
> determine if a server is a master or a standby. It makes tools that try to
> promote / demote a server more complicated, because they need to take this
> setting into account. Lastly, it breaks the new pg_basebackup -R
> functionality; pg_basebackup will create the recovery.conf file, but it
> won't take effect.

This patch breaks also pg_ctl promote because it always checks the existence of
$PGDATA/recovery.conf.

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2013-03-27 18:16:23 Re: [COMMITTERS] pgsql: Allow external recovery_config_directory
Previous Message Simon Riggs 2013-03-27 18:02:32 Re: [COMMITTERS] pgsql: Allow external recovery_config_directory

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2013-03-27 18:16:23 Re: [COMMITTERS] pgsql: Allow external recovery_config_directory
Previous Message Fujii Masao 2013-03-27 18:12:15 Re: Support for REINDEX CONCURRENTLY