MIME-Version: 1.0
References: 
 <CAJk5AtaqrHfzQ8iwdg0y3qvABfSn+HCr47O-Tj8pjtTKd3sTZA@mail.gmail.com>
 <CAA5-nLB8R0PTe_ENGdhmF=Sy5v4N_WxkMqRLUbs7885FZ2mAEw@mail.gmail.com>
 <CAJk5AtYnQupZSwBy2FgBG+uj5FXzg_7-bRFJtw+VW=XjD0oHvQ@mail.gmail.com>
In-Reply-To: 
 <CAJk5AtYnQupZSwBy2FgBG+uj5FXzg_7-bRFJtw+VW=XjD0oHvQ@mail.gmail.com>
From: Fabrice Chapuis <fabrice636861@gmail.com>
Date: Mon, 22 Dec 2025 12:44:23 +0100
Message-ID: 
 <CAA5-nLBNNvaRmasaBHGfn+1N+r_3Hazp8STR3pSCkT+oBXXV6w@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="0000000000007b3f5d064688f325"
Archived-At: 
 <https://www.postgresql.org/message-id/CAA5-nLBNNvaRmasaBHGfn%2B1N%2Br_3Hazp8STR3pSCkT%2BoBXXV6w%40mail.gmail.com>
Precedence: bulk

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

If it's a minor upgrade of the OS and Postgres, I perform the update in the
same time for all packages, starting with standby on a pre-production
environment.

On Mon, Dec 22, 2025 at 12:27=E2=80=AFPM Raj <rajeshkumar.dba09@gmail.com> =
wrote:

> 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, <fabrice636861@gmail.com>
> 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=E2=80=AFAM Raj <rajeshkumar.dba09@gmail.co=
m> 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
>>>
>>

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

<div dir=3D"ltr">If it&#39;s a minor upgrade of the OS and Postgres, I perf=
orm the update in the same time for all packages, starting with standby on =
a pre-production environment.</div><br><div class=3D"gmail_quote gmail_quot=
e_container"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Dec 22, 2025 at =
12:27=E2=80=AFPM Raj &lt;<a href=3D"mailto:rajeshkumar.dba09@gmail.com">raj=
eshkumar.dba09@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div dir=3D"auto">Thanks Anton.<div dir=3D"auto"><b=
r></div><div dir=3D"auto">@fabrice. We had compatibility checks already bef=
ore upgrade...but in a patroni cluster, what&#39;s the best approach a dba =
should recommended.</div><div dir=3D"auto"><br></div><div dir=3D"auto">1. D=
ont upgrade pgbackrest or postgres and exclude when performing os upgrade?<=
/div><div dir=3D"auto">2. Start upgrading DR first and then upgrade primary=
?</div><div dir=3D"auto">Etc ....</div></div><br><div class=3D"gmail_quote"=
><div dir=3D"ltr" class=3D"gmail_attr">On Mon, 22 Dec 2025, 16:45 Fabrice C=
hapuis, &lt;<a href=3D"mailto:fabrice636861@gmail.com" rel=3D"noreferrer" t=
arget=3D"_blank">fabrice636861@gmail.com</a>&gt; wrote:<br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi,<br>IMO the bes=
t thing to do is to check the release notes 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"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Dec=
 22, 2025 at 10:45=E2=80=AFAM Raj &lt;<a href=3D"mailto:rajeshkumar.dba09@g=
mail.com" rel=3D"noreferrer noreferrer" target=3D"_blank">rajeshkumar.dba09=
@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;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 - rh=
el 9.6,=C2=A0 postgres 17.6 in a patroni set up+ pgbackrest 2.6v) and in si=
te2(async standby - - rhel 9.6,=C2=A0 postgres 17.6 in a patroni set up+ pg=
backrest 2.6v)</div><div dir=3D"auto"><br></div><div dir=3D"auto">We have O=
S 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.</d=
iv><div dir=3D"auto"><br></div><div dir=3D"auto">Whereas db node in site3 i=
s no upgraded and stays with 9.6, 17.6 and 2.56 for rhel , postgres and pgb=
ackrest 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 upgra=
de 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?</div><div dir=3D"auto">Wha=
t wrong we are doing?</div><div dir=3D"auto">What is the right approach?=C2=
=A0</div><div dir=3D"auto">Any blogs is appreciated=C2=A0</div></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>

--0000000000007b3f5d064688f325--