| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: lost replication slots after pg_upgrade |
| Date: | 2020-10-13 16:33:49 |
| Message-ID: | 20201013163349.GE24889@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 13, 2020 at 06:20:41PM +0200, Pavel Stehule wrote:
> Hi
>
> One customer reports issue related to pg_upgrade.
>
> I found a thread https://www.postgresql-archive.org/
> Upgrade-and-re-synchronization-with-logical-replication-pglogical-and-PG-10-td6001990.html
>
> But I didn't find documentation of this limitation?
So, what is the question? Peter Eisentraut is right that WAL is not
preserved, so replication slots are not preserved. We do have
pg_upgrade instructions for upgrading binary replication, but I assume
people recreate the slots.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2020-10-13 16:37:14 | Re: lost replication slots after pg_upgrade |
| Previous Message | Heikki Linnakangas | 2020-10-13 16:30:28 | Re: partition routing layering in nodeModifyTable.c |