public inbox for [email protected]
help / color / mirror / Atom feedFrom: Raj <[email protected]>
To: Fabrice Chapuis <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: OS upgrade vs Postgresql
Date: Mon, 22 Dec 2025 16:57:39 +0530
Message-ID: <CAJk5AtYnQupZSwBy2FgBG+uj5FXzg_7-bRFJtw+VW=XjD0oHvQ@mail.gmail.com> (raw)
In-Reply-To: <CAA5-nLB8R0PTe_ENGdhmF=Sy5v4N_WxkMqRLUbs7885FZ2mAEw@mail.gmail.com>
References: <CAJk5AtaqrHfzQ8iwdg0y3qvABfSn+HCr47O-Tj8pjtTKd3sTZA@mail.gmail.com>
<CAA5-nLB8R0PTe_ENGdhmF=Sy5v4N_WxkMqRLUbs7885FZ2mAEw@mail.gmail.com>
Thanks Anton.
@fabrice. We had compatibility checks already before upgrade...but in a
patroni cluster, what's the best approach a dba should recommended.
1. Dont upgrade pgbackrest or postgres and exclude when performing os
upgrade?
2. Start upgrading DR first and then upgrade primary?
Etc ....
On Mon, 22 Dec 2025, 16:45 Fabrice Chapuis, <[email protected]> wrote:
> Hi,
> IMO the best thing to do is to check the release notes for PG 17.7 and
> pgbackrest 2.57.
> Generally speaking, there are no compatibility issues between minor
> versions of Postgres.
> Regards,
> Fabrice
>
> On Mon, Dec 22, 2025 at 10:45 AM Raj <[email protected]> wrote:
>
>> Hi team,
>>
>> Our set up is Site1(primary - rhel 9.6, postgres 17.6 in a patroni set
>> up+ pgbackrest 2.6v & sync replica - - rhel 9.6, postgres 17.6 in a
>> patroni set up+ pgbackrest 2.6v) and in site2(async standby - - rhel 9.6,
>> postgres 17.6 in a patroni set up+ pgbackrest 2.6v)
>>
>> We have OS upgrade from rhel 9.6 to 9.7 for two nodes in Site1. We can
>> see postgres and pgbackrest has automatically upgraded to 17.7 and 2.57
>> respectively.
>>
>> Whereas db node in site3 is no upgraded and stays with 9.6, 17.6 and 2.56
>> for rhel , postgres and pgbackrest version respectively.this will be
>> upgraded tomorrow
>>
>> Is this a problem( we intend to upgrade only OS and not postgres) ? Is
>> this problem or is it best way or is it a normal behaviour that can or
>> should be avoided?
>> What wrong we are doing?
>> What is the right approach?
>> Any blogs is appreciated
>>
>
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]
Subject: Re: OS upgrade vs Postgresql
In-Reply-To: <CAJk5AtYnQupZSwBy2FgBG+uj5FXzg_7-bRFJtw+VW=XjD0oHvQ@mail.gmail.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