public inbox for [email protected]
help / color / mirror / Atom feedFrom: BUBACZ Martin <[email protected]>
To: [email protected] <[email protected]>
Subject: Upgrade Failover Cluster
Date: Thu, 4 Dec 2025 06:59:52 +0000
Message-ID: <DU2PR04MB8631002517CF55E7E48B6FB1E3A6A@DU2PR04MB8631.eurprd04.prod.outlook.com> (raw)
Hi All,
I'm fairly new to postgresql and I have a question concerning upgrading a 2 node failover physical replication cluster. I'm automating the cluster installation and maintenance by using Puppet. All runs good so far.
When it comes to an upgrade scenario, let's say upgrading from rel. 16.x to 17.x, I'm unsure if it is required to upgrade primary first and then replica or if order doesn't matter. I've read different statements in some articles on internet about it. One said it's possible to upgrade replica first by using pg_upgrade or rebuilding replica from primary by pg_basebackup and others are telling me primary first.
What is the recommended/most stable path to upgrade a cluster? I would appreciate if you could shed some light on this? Thanks beforehand.
Regards,
[http://intranet/pb/site/intranet/get/documents/intraxa/PB7-Datenquelle/Ressorts/Vorstandsvorsitzende...]
Martin BUBACZ
Database Administrator (Oracle)
Global Intermediate Products Oracle
Global Service Operations
AXA Group Operations
AXA Group Operations
Colonia-Allee 10-20
51067 Köln
Germany
Tel.: +49 221 148 21934
Fax: +49 221 148 44 21934
[email protected]<mailto:[email protected]>
axa.de / axa.be<http://www.axa.de/;
[http://intranet/pb/site/intranet/get/documents/intraxa/PB7-Datenquelle/Ressorts/Vorstandsvorsitzende...]<https://www.facebook.com/AXA.de; [http://intranet/pb/site/intranet/get/documents/intraxa/PB7-Datenquelle/Ressorts/Vorstandsvorsitzende...] <https://twitter.com/axadeutschland; [http://intranet/pb/site/intranet/get/documents/intraxa/PB7-Datenquelle/Ressorts/Vorstandsvorsitzende...] <https://www.xing.com/companies/axa; [http://intranet/pb/site/intranet/get/documents/intraxa/PB7-Datenquelle/Ressorts/Vorstandsvorsitzende...] <https://www.instagram.com/axa_deutschland;
Please consider the environment before printing this e-mail. Thank you.
Scheduled Absence: 22.12.2025-11.01.2026
Internal
=========================================================================
AXA Group Operations Germany GmbH
Sitz der Gesellschaft: Köln
Handelsregister: Köln HR B Nr. 22372
Geschäftsführer: Helmut Schmidt
-------------------------------------------------------------------------
Der Inhalt dieser E-Mail ist vertraulich und ausschliesslich fuer den
bezeichneten Adressaten oder dessen Vertreter bestimmt. Sollten Sie
nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein,
so bitten wir Sie, sich mit dem Absender der E-Mail in Verbindung zu
setzen. Beachten Sie bitte, dass jede Form der unautorisierten Nutzung,
Veroeffentlichung, Vervielfaeltigung oder Weitergabe des Inhaltes dieser
E-Mail nicht gestattet ist.
-------------------------------------------------------------------------
This message contains confidential information and is exclusively for the
person addressed or their representative. If you are not the intended
recipient of this message and its contents, please notify the sender
immediately. Any form of unauthorised use, publication, reproduction,
copying or disclosure of the content of the e-mail is not permitted.
=========================================================================
Attachments:
[image/jpeg] image001.jpg (1.1K, 3-image001.jpg)
download | view image
[image/png] image002.png (1.5K, 4-image002.png)
download | view image
[image/png] image003.png (1.6K, 5-image003.png)
download | view image
[image/png] image004.png (1.7K, 6-image004.png)
download | view image
[image/png] image005.png (1.8K, 7-image005.png)
download | view image
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]
Subject: Re: Upgrade Failover Cluster
In-Reply-To: <DU2PR04MB8631002517CF55E7E48B6FB1E3A6A@DU2PR04MB8631.eurprd04.prod.outlook.com>
* 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