Re: Dividing progress/debug information in pg_standby, and stat before copy

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: Dividing progress/debug information in pg_standby, and stat before copy
Дата
Msg-id 4B5ECA44.9080108@enterprisedb.com
обсуждение исходный текст
Ответ на Re: Dividing progress/debug information in pg_standby, and stat before copy  (Dimitri Fontaine <dfontaine@hi-media.com>)
Список pgsql-hackers
Dimitri Fontaine wrote:
> Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
>> Yes. Just like with pg_standby.
> 
> Hehe, I'm using walmgr.py from skytools instead, and this discussion
> makes me think I'll continue doing so even if using SR, as they are
> complementary solutions.
> 
> In SR mode, the master continues to archive as usual, and the slave will
> either take the WAL on a per-file basis from the restore_command or on
> an per-LSN basis from the walreceiver and a live connection to the
> master, right?

Right.

> Does it mean any working wal shipping setup (pitrtools, walmgr.py) will
> continue working unchanged, or should we begin testing those and
> scheduling adaptations to 9.0?

They will continue to work as is, just leave standby_mode=off. But if
you want to take advantage streaming replication, you'll have to switch
it to 'on', and adapt the scripts to work with that.

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com


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

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Dividing progress/debug information in pg_standby, and stat before copy
Следующее
От: "David E. Wheeler"
Дата:
Сообщение: Re: Review: listagg aggregate