From: Victor Sudakov <vas@sibptus.ru>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Upgrading Patroni from 2.1.x to 3.0.1 ?
Date: Sun, 19 Mar 2023 07:28:21 +0000
Message-ID: <ZBa5lR/NiB3K02K0@admin.sibptus.ru> (raw)
In-Reply-To: <ZAWsyLajuJpIDdz8@admin.sibptus.ru>
References: <ZAWsyLajuJpIDdz8@admin.sibptus.ru>
Victor Sudakov wrote:
>
> Did you encounter any problems upgrading Patroni from 2.1.x to 3.0.1 ?
>
> What's the recommended procedure, did you stop all cluster members
> (the patroni service and PostgreSQL instances themselves) before this
> major version upgrade?
In case someone has the same question. The upgrade did not cause any
problems and 3.0.1 seems backward compatible with 2.1.x.
I just stopped tne Patroni service on a cluster node, upgraded Patroni
and started the node with a new version, with no problems encountered.
I'm missing the cluster ID in the `patronictl list` output a bit.
--
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet
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: pgsql-admin@postgresql.org
Cc: vas@sibptus.ru, pgsql-admin@lists.postgresql.org
Subject: Re: Upgrading Patroni from 2.1.x to 3.0.1 ?
In-Reply-To: <ZBa5lR/NiB3K02K0@admin.sibptus.ru>
* 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