| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, "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> |
| Subject: | Re: pg_upgrade and logical replication |
| Date: | 2023-09-20 23:08:59 |
| Message-ID: | ZQt7ixloBQbl0FZF@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 20, 2023 at 04:54:36PM +0530, Amit Kapila wrote:
> Also, the patch seems to be allowing subscription relations from PG
> >=10 to be migrated but how will that work if the corresponding
> publisher is also upgraded without slots? Won't the corresponding
> workers start failing as soon as you restart the upgrade server? Do we
> need to document the steps for users?
Hmm? How is that related to the upgrade of the subscribers? And how
is that different from the case where a subscriber tries to connect
back to a publisher where a slot has been dropped? There is no need
of pg_upgrade to reach such a state:
ERROR: could not start WAL streaming: ERROR: replication slot "popo" does not exist
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-09-20 23:14:23 | Re: Add 'worker_type' to pg_stat_subscription |
| Previous Message | Peter Smith | 2023-09-20 23:01:01 | Re: Add 'worker_type' to pg_stat_subscription |