From: | Axel Rau <Axel(dot)Rau(at)chaos1(dot)de> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: restarting logical replication after upgrading standby |
Date: | 2022-02-07 17:00:01 |
Message-ID: | c534c888-93dd-48e0-fb31-4798bc1ac6c0@Chaos1.DE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks Vijay for all your work, you have done to help me to resolve this
issue.
Am 06.02.22 um 20:03 schrieb Vijaykumar Jain:
> *# so finally, i truncate the table and re-sync :(
I'm disappointed. )-:
and everything works,
> but i think i am missing something here. i am pretty sure we *
> *# can play with pg_replication_origin_advance
> or pg_replication_slot_advance to move the lsn to continue subscription
> without a sync, i'll have to spend some time to understand that*
> *# but for now, in summary, subscription breaks in upgrade. After an
> upgrade, we need to enable it back and possibly refresh publication
> (re-sync) from scratch.*
> *# but i am hoping i can be corrected by more experienced people here.*
Anybody out there, succeeding with upgrading a logical replication
subscriber without resyncing it?
Any help appreciated,
Axel
--
PGP-Key: CDE74120 ☀ computing @ chaos claudius
From | Date | Subject | |
---|---|---|---|
Next Message | Victor Sudakov | 2022-02-08 03:34:28 | Re: Lost replication slots after pg_upgrade. |
Previous Message | Laurenz Albe | 2022-02-07 16:09:20 | Re: autovacuum default run with vacuum_index_cleanup and vacuum_truncate and related lock? |