public inbox for [email protected]  
help / color / mirror / Atom feed
From: Michael Banck <[email protected]>
To: Klaus Darilion <[email protected]>
Cc: Mahesh Sathe <[email protected]>
Cc: Raj <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: Major upgrade in patroni cluster
Date: Mon, 6 Jul 2026 12:52:10 +0200
Message-ID: <[email protected];lightning.p46.dedyn.io> (raw)
In-Reply-To: <DBAPR03MB635872C763EDC6BC1DFE7FA4F1F12@DBAPR03MB6358.eurprd03.prod.outlook.com>
References: <CAJk5Atax1egLDrB3YUb1+q5kGfyFpMsN0H5djSacL309k5C28Q@mail.gmail.com>
	<CAG6Sa9Uz9_WTq7u2Zm6VJaJDvYh-vVbqbwstvARj6CJ7f3EGew@mail.gmail.com>
	<DBAPR03MB635872C763EDC6BC1DFE7FA4F1F12@DBAPR03MB6358.eurprd03.prod.outlook.com>

On Mon, Jul 06, 2026 at 10:43:52AM +0000, Klaus Darilion wrote:
> Do I understand it right, that during the rolling upgrade you loose
> High Availability as for short time the Patroni nodes use a different
> Postgres version and hence the streaming replication will not work?

That is correct, and short of using logical replication for
zero-downtime upgrade into a separate, new, Patroni cluster, I don't see
how to circumvent this.

One can make the upgrade window smaller by upgrading the standbys with
rsync, but that is quite brittle and should only be done in controlled
environments after lots of testing. Also, it only works with the --link
pg_upgrade option, not --copy or --clone.


Michael





view thread (5+ messages)  latest in thread

reply

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 using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Major upgrade in patroni cluster
  In-Reply-To: <[email protected];lightning.p46.dedyn.io>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox