public inbox for [email protected]help / color / mirror / Atom feed
OS upgrade vs Postgresql 4+ messages / 2 participants [nested] [flat]
* OS upgrade vs Postgresql @ 2025-12-22 09:44 Raj <[email protected]> 2025-12-22 11:15 ` Re: OS upgrade vs Postgresql Fabrice Chapuis <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Raj @ 2025-12-22 09:44 UTC (permalink / raw) To: Pgsql-admin <[email protected]> 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 ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: OS upgrade vs Postgresql 2025-12-22 09:44 OS upgrade vs Postgresql Raj <[email protected]> @ 2025-12-22 11:15 ` Fabrice Chapuis <[email protected]> 2025-12-22 11:27 ` Re: OS upgrade vs Postgresql Raj <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Fabrice Chapuis @ 2025-12-22 11:15 UTC (permalink / raw) To: Raj <[email protected]>; +Cc: Pgsql-admin <[email protected]> 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 > ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: OS upgrade vs Postgresql 2025-12-22 09:44 OS upgrade vs Postgresql Raj <[email protected]> 2025-12-22 11:15 ` Re: OS upgrade vs Postgresql Fabrice Chapuis <[email protected]> @ 2025-12-22 11:27 ` Raj <[email protected]> 2025-12-22 11:44 ` Re: OS upgrade vs Postgresql Fabrice Chapuis <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Raj @ 2025-12-22 11:27 UTC (permalink / raw) To: Fabrice Chapuis <[email protected]>; +Cc: Pgsql-admin <[email protected]> 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 >> > ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: OS upgrade vs Postgresql 2025-12-22 09:44 OS upgrade vs Postgresql Raj <[email protected]> 2025-12-22 11:15 ` Re: OS upgrade vs Postgresql Fabrice Chapuis <[email protected]> 2025-12-22 11:27 ` Re: OS upgrade vs Postgresql Raj <[email protected]> @ 2025-12-22 11:44 ` Fabrice Chapuis <[email protected]> 0 siblings, 0 replies; 4+ messages in thread From: Fabrice Chapuis @ 2025-12-22 11:44 UTC (permalink / raw) To: Raj <[email protected]>; +Cc: Pgsql-admin <[email protected]> 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 PM Raj <[email protected]> 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, <[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 >>> >> ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2025-12-22 11:44 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-12-22 09:44 OS upgrade vs Postgresql Raj <[email protected]> 2025-12-22 11:15 ` Fabrice Chapuis <[email protected]> 2025-12-22 11:27 ` Raj <[email protected]> 2025-12-22 11:44 ` Fabrice Chapuis <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox