From: Alan Hodgson <ahodgson@lists.simkin.ca>
To: pgsql-general@lists.postgresql.org
Subject: Re: Trying to understand a failed upgrade in AWS RDS
Date: Tue, 23 May 2023 08:02:20 -0700
Message-ID: <327a821bc88b41fc15cc04f18695e2d20d874312.camel@lists.simkin.ca> (raw)
In-Reply-To: <CAMp9=Ey06atDdY6a=Z93NsMETFpojNw7J+JnF-CxT9aTYgW4zg@mail.gmail.com>
References: <CAMp9=Ezf9OyuQaQUZDHEauTp-Dn_pPdS6xNmcFJHuQM_qsmZvQ@mail.gmail.com>
<CAMp9=Eze3TsZ9rdWqh0NSM1gYjKYX8onf0zF2nuc_k3Szw0iPw@mail.gmail.com>
<CACoOY7ZkFJYCRrN5sxwxRG-=TWaQVH4oSi5Mp86w8aLNztwWTQ@mail.gmail.com>
<CAMp9=EzwL1cYBWqFkT5SEJvJg6uRfUpWwpWgMUcmUcK9heSHhQ@mail.gmail.com>
<CAOBaU_ZoT18AFxLo24iAtHQr3xF9whix++EOPpMW5KMP6fWSsA@mail.gmail.com>
<CAMp9=Ey06atDdY6a=Z93NsMETFpojNw7J+JnF-CxT9aTYgW4zg@mail.gmail.com>
On Sun, 2023-05-21 at 07:56 -0700, Mike Lissner wrote:
> > As far as I know it's impossible to reliably pg_upgrade a node
> > that has subscriptions and eventually resume logical
> > replication.
> >
>
>
> Should this go in the documentation somewhere? Maybe in the
> pg_upgrade notes? I still don't understand the mechanism. You also
> say that:
>
> > It's possible to make it work with some efforts in some basic
> > configurations and / or if no changes happen on the publications
> >
>
>
> But that kind of surprises me too, actually, because it seemed like
> pg_upgrade wiped out the LSN locations of the subcriber, making it
> start all over.
>
> Upgrading a subscriber seems like something that could/should work,
> so it should be documented if pg_upgrade is incompatible with
> maintaining a subscription, shouldn't it?
The docs are strangely silent on this. AFAIK pg_upgrade on either the
publisher or subscriber breaks logical replication, which does make
sense since pg_upgrade basically makes a new database cluster as it
runs.
There is a way to manually set the LSN position of an enabled=false
replication slot, but I've failed to make that work right in tests so
far.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ahodgson@lists.simkin.ca
Subject: Re: Trying to understand a failed upgrade in AWS RDS
In-Reply-To: <327a821bc88b41fc15cc04f18695e2d20d874312.camel@lists.simkin.ca>
References: <CAMp9=Ezf9OyuQaQUZDHEauTp-Dn_pPdS6xNmcFJHuQM_qsmZvQ@mail.gmail.com> <CAMp9=Eze3TsZ9rdWqh0NSM1gYjKYX8onf0zF2nuc_k3Szw0iPw@mail.gmail.com> <CACoOY7ZkFJYCRrN5sxwxRG-=TWaQVH4oSi5Mp86w8aLNztwWTQ@mail.gmail.com> <CAMp9=EzwL1cYBWqFkT5SEJvJg6uRfUpWwpWgMUcmUcK9heSHhQ@mail.gmail.com> <CAOBaU_ZoT18AFxLo24iAtHQr3xF9whix++EOPpMW5KMP6fWSsA@mail.gmail.com> <CAMp9=Ey06atDdY6a=Z93NsMETFpojNw7J+JnF-CxT9aTYgW4zg@mail.gmail.com> <327a821bc88b41fc15cc04f18695e2d20d874312.camel@lists.simkin.ca>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox