Re: Trying to understand a failed upgrade in AWS RDS - Mailing list pgsql-general

From Mike Lissner
Subject Re: Trying to understand a failed upgrade in AWS RDS
Date
Msg-id CAMp9=Ey06atDdY6a=Z93NsMETFpojNw7J+JnF-CxT9aTYgW4zg@mail.gmail.com
Whole thread Raw
In response to Re: Trying to understand a failed upgrade in AWS RDS  (Julien Rouhaud <rjuju123@gmail.com>)
Responses Re: Trying to understand a failed upgrade in AWS RDS
List 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?

pgsql-general by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Profiling a function call
Next
From: "Theodore M Rolle, Jr."
Date:
Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?