Re: [COMMITTERS] pgsql: Allow external recovery_config_directory
| От | Heikki Linnakangas |
|---|---|
| Тема | Re: [COMMITTERS] pgsql: Allow external recovery_config_directory |
| Дата | |
| Msg-id | 51535F16.2020602@vmware.com обсуждение исходный текст |
| Ответ на | Re: [COMMITTERS] pgsql: Allow external recovery_config_directory (Simon Riggs <simon@2ndQuadrant.com>) |
| Ответы |
Re: [COMMITTERS] pgsql: Allow external recovery_config_directory
Re: [COMMITTERS] pgsql: Allow external recovery_config_directory |
| Список | 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 по дате отправления: