Re: lost replication slots after pg_upgrade

Поиск
Список
Период
Сортировка
Искать
От
Peter Eisentraut
Тема
Re: lost replication slots after pg_upgrade
Дата
Msg-id
b9aec528-f2a0-7ab0-4350-c95701b4ecce@2ndquadrant.com
Ответ на
Список
Дерево обсуждения
lost replication slots after pg_upgrade Pavel Stehule <pavel.stehule@gmail.com>
Re: lost replication slots after pg_upgrade Bruce Momjian <bruce@momjian.us>
Re: lost replication slots after pg_upgrade Pavel Stehule <pavel.stehule@gmail.com>
Re: lost replication slots after pg_upgrade Bruce Momjian <bruce@momjian.us>
Re: lost replication slots after pg_upgrade Pavel Stehule <pavel.stehule@gmail.com>
Re: lost replication slots after pg_upgrade Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: lost replication slots after pg_upgrade Bruce Momjian <bruce@momjian.us>
On 2020-10-13 19:23, Pavel Stehule wrote:
> no, I just missi note, so after upgrade by pg_upgrade I have to recreate 
> replication slots. Some like
> 
> after pg_upgrade you should to do:
> 
> a) run analyze .... (it is a known case)
> b) recreate replication slots - these slots are not removed in the 
> upgrade process.

An argument could be made that pg_upgrade should copy over logical 
replication slots.  The normal scenario would be that you pause your 
logical subscriptions, run pg_upgrade on the publisher, then un-pause 
the subscriptions.  The subscribers then ought to be able to reconnect 
and continue consuming logical changes.  Since the content of the 
publisher database is logically the same before and after the upgrade, 
this should appear transparent to the subscribers.  They'll just see 
that the publisher was offline for a while.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


В списке pgsql-hackers по дате отправления
От: Russell Foster
Дата:
От: Bruce Momjian
Дата:
FAQ