Re: a new standby server promotes itself to primary without cause

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: a new standby server promotes itself to primary without cause
Дата
Msg-id 56182770.9050700@gmx.net
обсуждение исходный текст
Ответ на Re: a new standby server promotes itself to primary without cause  (Scott Mead <scottm@openscg.com>)
Список pgsql-admin
On 10/8/15 11:04 AM, Scott Mead wrote:
>     restore_command = 'cp /var/lib/pgsql/9.4/share/%f %p'           #
>     e.g. 'cp /mnt/server/archivedir/%f %p'
>     archive_cleanup_command = '/usr/pgsql-9.4/bin/pg_archivecleanup
>     /var/lib/pgsql/9.4/share %r'
>     #recovery_end_command = ''
>     #recovery_target_name = ''      # e.g. 'daily backup 2011-01-26'
>     #recovery_target_time = ''      # e.g. '2004-07-14 22:39:00 EST'
>     #recovery_target_xid = ''
>     #recovery_target_inclusive = true
>     recovery_target = 'immediate'
>
>
> I believe you should omit recovery_target.
> From http://www.postgresql.org/docs/9.4/static/recovery-target-settings.html
>
> recovery_target = 'immediate'
>
>     This parameter specifies that recovery should end as soon as a
>     consistent state is reached, i.e. as early as possible. When
>     restoring from an online backup, this means the point where taking
>     the backup ended.

Seems kind of weird that that would override the setting for standby_mode.

Isn't standby_mode = on effectively recovery_target = 'infinity'?



В списке pgsql-admin по дате отправления:

Предыдущее
От: dinesh bhandary
Дата:
Сообщение: Re: streaming rep setup in PCI compliance environment
Следующее
От: Scott Ribe
Дата:
Сообщение: Re: streaming rep setup in PCI compliance environment