| From: | Mike Lissner <mlissner(at)michaeljaylissner(dot)com> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | "Elterman, Michael" <melterman(at)enova(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Trying to understand a failed upgrade in AWS RDS |
| Date: | 2023-05-21 14:56:00 |
| Message-ID: | CAMp9=Ey06atDdY6a=Z93NsMETFpojNw7J+JnF-CxT9aTYgW4zg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Theodore M Rolle, Jr. | 2023-05-21 17:15:38 | Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? |
| Previous Message | Pavel Stehule | 2023-05-21 11:42:50 | Re: Profiling a function call |