From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [COMMITTERS] pgsql: Allow external recovery_config_directory |
Date: | 2013-03-27 17:50:05 |
Message-ID: | 5153314D.5080902@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 27.03.2013 19:34, Simon Riggs wrote:
> On 27 March 2013 16:24, Heikki Linnakangas<hlinnakangas(at)vmware(dot)com> wrote:
>> Lastly, it breaks the new pg_basebackup -R
>> functionality; pg_basebackup will create the recovery.conf file, but it
>> won't take effect.
>
> AFAIK pg_basebackup doesn't backup files not in the data directory and
> tablespace dirs.
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.
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2013-03-27 17:58:26 | Re: [COMMITTERS] pgsql: Allow external recovery_config_directory |
Previous Message | Simon Riggs | 2013-03-27 17:34:47 | Re: [COMMITTERS] pgsql: Allow external recovery_config_directory |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2013-03-27 17:58:26 | Re: [COMMITTERS] pgsql: Allow external recovery_config_directory |
Previous Message | Simon Riggs | 2013-03-27 17:34:47 | Re: [COMMITTERS] pgsql: Allow external recovery_config_directory |