From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | vignesh C <vignesh21(at)gmail(dot)com> |
Cc: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Subject: | Re: pg_upgrade and logical replication |
Date: | 2023-09-25 01:57:28 |
Message-ID: | ZRDpCNgrD1-7KwQS@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 20, 2023 at 09:38:56AM +0900, Michael Paquier wrote:
> And this code path is used to start postmaster instances for old and
> new clusters. So it seems to me that it is incorrect if this is not
> conditional based on the cluster version.
Avoiding the startup of bgworkers during pg_upgrade is something that
worries me a bit, actually, as it could be useful in some cases like
monitoring? That would be fancy, for sure.. For now and seeing a
lack of consensus on this larger matter, I'd like to propose a check
for IsBinaryUpgrade into ApplyLauncherRegister() instead as it makes
no real sense to start apply workers in this context. That would be
equivalent to max_logical_replication_workers = 0.
Amit, Vignesh, would the attached be OK for both of you?
(Vignesh has posted a slightly different version of this patch on a
different thread, but the subscriber part should be part of this
thread with the subscribers, I assume.)
--
Michael
Attachment | Content-Type | Size |
---|---|---|
0001-Prevent-startup-of-logical-replication-launcher-in-b.patch | text/x-diff | 2.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Smith | 2023-09-25 02:13:59 | Re: Synchronizing slots from primary to standby |
Previous Message | Michael Paquier | 2023-09-25 00:56:22 | Re: Doesn't pgstat_report_wal() handle the argument "force" incorrectly |