Re: pg_upgrade and logical replication
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Peter Smith <smithpb2250@gmail.com>
Cc: vignesh C <vignesh21@gmail.com>, Michael Paquier <michael@paquier.xyz>, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>,
Julien Rouhaud <rjuju123@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-11-30T02:58:24Z
Lists: pgsql-hackers
On Thu, Nov 30, 2023 at 6:37 AM Peter Smith <smithpb2250@gmail.com> wrote: > > Here are some review comments for patch v20-0001 > > ====== > > 1. getSubscriptions > > + if (dopt->binary_upgrade && fout->remoteVersion >= 170000) > + appendPQExpBufferStr(query, " s.subenabled\n"); > + else > + appendPQExpBufferStr(query, " false AS subenabled\n"); > > Probably I misunderstood this logic... AFAIK the CREATE SUBSCRIPTION > is normally default *enabled*, so why does this code set default > differently as 'false'. OTOH, if this is some special case default > needed because the subscription upgrade is not supported before PG17 > then maybe it needs a comment to explain. > Yes, it is for prior versions. By default subscriptions are restored disabled even if they are enabled before dump. See docs [1] for reasons (When dumping logical replication subscriptions, ..). I don't think we need a comment here as that is a norm we use at other similar places where we do version checking. We can argue that there could be more comments as to why the 'connect' is false and if those are really required, we should do that as a separate patch. [1] - https://www.postgresql.org/docs/devel/app-pgdump.html -- With Regards, Amit Kapila.
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