Re: pg_upgrade and logical replication
vignesh C <vignesh21@gmail.com>
From: vignesh C <vignesh21@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: Julien Rouhaud <rjuju123@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Amit Kapila <amit.kapila16@gmail.com>
Date: 2023-09-15T11:21:57Z
Lists: pgsql-hackers
On Fri, 15 Sept 2023 at 15:08, vignesh C <vignesh21@gmail.com> wrote: > > On Tue, 12 Sept 2023 at 14:25, Hayato Kuroda (Fujitsu) > <kuroda.hayato@fujitsu.com> wrote: > > > > Dear Vignesh, > > > > Thank you for updating the patch! Here are some comments. > > > > Sorry if there are duplicate comments - the thread revived recently so I might > > lose my memory. > > > > 01. General > > > > Is there a possibility that apply worker on old cluster connects to the > > publisher during the upgrade? Regarding the pg_upgrade on publisher, the we > > refuse TCP/IP connections from remotes and port number is also changed, so we can > > assume that subscriber does not connect to. But IIUC such settings may not affect > > to the connection source, so that the apply worker may try to connect to the > > publisher. Also, is there any hazards if it happens? > > Yes, there is a possibility that the apply worker gets started and new > transaction data is being synced from the publisher. I have made a fix > not to start the launcher process in binary ugprade mode as we don't > want the launcher to start apply worker during upgrade. Another approach to solve this as suggested by one of my colleague Hou-san would be to set max_logical_replication_workers = 0 while upgrading. I will evaluate this and update the next version of patch accordingly. Regards, Vignesh
Commits
-
pg_upgrade: Retrieve subscription count more efficiently.
- 73de50e13e39 17.0 landed
- 364509a2e7f9 18.0 landed
-
Fix random failure in 004_subscription.
- 677a45c4ae16 17.0 landed
-
Fix 004_subscription.pl to allow its usage in --link mode.
- f17529b71097 17.0 landed
-
Allow upgrades to preserve the full subscription's state.
- 9a17be1e244a 17.0 landed
-
Prevent startup of logical replication launcher during pg_upgrade
- 7021d3b17664 17.0 landed