MIME-Version: 1.0
References: 
 <CAJk5AtaqrHfzQ8iwdg0y3qvABfSn+HCr47O-Tj8pjtTKd3sTZA@mail.gmail.com>
In-Reply-To: 
 <CAJk5AtaqrHfzQ8iwdg0y3qvABfSn+HCr47O-Tj8pjtTKd3sTZA@mail.gmail.com>
From: Fabrice Chapuis <fabrice636861@gmail.com>
Date: Mon, 22 Dec 2025 12:15:06 +0100
Message-ID: 
 <CAA5-nLB8R0PTe_ENGdhmF=Sy5v4N_WxkMqRLUbs7885FZ2mAEw@mail.gmail.com>
Subject: Re: OS upgrade vs Postgresql
To: Raj <rajeshkumar.dba09@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000cad1800646888ab0"
Archived-At: 
 <https://www.postgresql.org/message-id/CAA5-nLB8R0PTe_ENGdhmF%3DSy5v4N_WxkMqRLUbs7885FZ2mAEw%40mail.gmail.com>
Precedence: bulk

--000000000000cad1800646888ab0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFAM Raj <rajeshkumar.dba09@gmail.com> =
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 se=
e
> 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
>

--000000000000cad1800646888ab0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<br>IMO the best thing to do is to check the release no=
tes for PG 17.7 and=C2=A0

pgbackrest 2.57.<br>Generally speaking, there are no compatibility issues b=
etween minor versions of Postgres.<br>Regards,<div>Fabrice</div></div><br><=
div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"g=
mail_attr">On Mon, Dec 22, 2025 at 10:45=E2=80=AFAM Raj &lt;<a href=3D"mail=
to:rajeshkumar.dba09@gmail.com">rajeshkumar.dba09@gmail.com</a>&gt; wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto=
">Hi team,<div dir=3D"auto"><br></div><div dir=3D"auto">Our set up is Site1=
(primary - rhel 9.6,=C2=A0 postgres 17.6 in a patroni set up+ pgbackrest 2.=
6v=C2=A0 =C2=A0&amp; sync replica -=C2=A0 - rhel 9.6,=C2=A0 postgres 17.6 i=
n a patroni set up+ pgbackrest 2.6v) and in site2(async standby - - rhel 9.=
6,=C2=A0 postgres 17.6 in a patroni set up+ pgbackrest 2.6v)</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">We have OS upgrade from rhel 9.6 to 9=
.7 for two nodes in Site1. We can see postgres and pgbackrest has automatic=
ally upgraded to 17.7 and 2.57 respectively.</div><div dir=3D"auto"><br></d=
iv><div dir=3D"auto">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</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">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 o=
r should be avoided?</div><div dir=3D"auto">What wrong we are doing?</div><=
div dir=3D"auto">What is the right approach?=C2=A0</div><div dir=3D"auto">A=
ny blogs is appreciated=C2=A0</div></div>
</blockquote></div>

--000000000000cad1800646888ab0--