Message-ID: <64901959.050a0220.f396a.9554@mx.google.com>
Sender: Michael Banck <mbanck@gmail.com>
Date: Mon, 19 Jun 2023 11:01:12 +0200
From: Michael Banck <mbanck@gmx.net>
To: James Cloos <cloos@jhcloos.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: =?utf-8?B?ZGVi4oCZ?= =?utf-8?Q?s?= pg_upgradecluster(1) vs
 streaming replication
References: <m3ilblvg68.fsf@carbon.jhcloos.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <m3ilblvg68.fsf@carbon.jhcloos.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://www.postgresql.org/message-id/64901959.050a0220.f396a.9554%40mx.google.com>
Precedence: bulk

Hi,

On Sat, Jun 17, 2023 at 07:10:23PM -0400, James Cloos wrote:
> Has anyone recently tried updating a streaming replication cluster using
> debian’s pg_upgradecluster(1) on each node?

Note that the word "cluster" in upgradecluster refers to a single
Postgres instance, a.k.a a cluster of databases. It is not designed to
upgrade streaming replication clusters.

> Did things work well?
> 
> My last attempt (11 to 13, as I recall) had issues and I had to drop and
> re-install the db on the secondaries.
> 
> I'd like to avoid that this time...
> 
> Should I expect things to work easily?

No, you need to either rebuild the secondaries or use the rsync method
to resync them from the documentation. The latter is complicated and
iffy though, and not generally recommended I believe.


Michael