Re: lost replication slots after pg_upgrade - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: lost replication slots after pg_upgrade
Date
Msg-id b9aec528-f2a0-7ab0-4350-c95701b4ecce@2ndquadrant.com
Whole thread Raw
In response to Re: lost replication slots after pg_upgrade  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: lost replication slots after pg_upgrade  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
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 by date:

Previous
From: Russell Foster
Date:
Subject: Re: [Patch] Using Windows groups for SSPI authentication
Next
From: Bruce Momjian
Date:
Subject: Re: lost replication slots after pg_upgrade