From: | Victor Sudakov <vas(at)sibptus(dot)ru> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Upgrading Patroni from 2.1.x to 3.0.1 ? |
Date: | 2023-03-19 07:28:21 |
Message-ID: | ZBa5lR/NiB3K02K0@admin.sibptus.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(at)fidonet
From | Date | Subject | |
---|---|---|---|
Next Message | Debraj Manna | 2023-03-19 09:02:23 | How to pass idle_session_timeout in postgres docker in a compose file? |
Previous Message | Keith Fiske | 2023-03-15 18:53:29 | Re: Automatic partition creation? |