Re: [COMMITTERS] pgsql: Allow external recovery_config_directory - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: [COMMITTERS] pgsql: Allow external recovery_config_directory
Date
Msg-id 51535F16.2020602@vmware.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Allow external recovery_config_directory  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: [COMMITTERS] pgsql: Allow external recovery_config_directory  (Simon Riggs <simon@2ndQuadrant.com>)
Re: [COMMITTERS] pgsql: Allow external recovery_config_directory  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On 27.03.2013 20:02, Simon Riggs wrote:
> On 27 March 2013 17:50, Heikki Linnakangas<hlinnakangas@vmware.com>  wrote:
>> Imagine that you have set recovery_config_directory='/foo/' in the master
>> server. Now you want to set up a standby, so you do:'
>>
>> pg_basebackup -D data-standby -R
>>
>> With the -R option, pg_basebackup creates data-standby/recovery.conf to
>> point to the master, with standby_mode='on'. But if you start the server, it
>> will start up as a master, not as a standby, because
>> recovery_config_directory points elsewhere.
>
> Yeh, I get it.
>
> Same argument applies to all conf files, not just recovery.conf.
>
> Sounds like the patch to add -R to pg_basebackup should be revoked as
> being not well thought out. Or it should be fixed, in which case this
> works the same.

What exactly was wrong with pg_basebackup -R, without 
recovery_config_directory?

- Heikki



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pkg-config files for libpq and ecpg
Next
From: Tom Lane
Date:
Subject: Re: pkg-config files for libpq and ecpg