Hi
Kindly share the best way in this scenario, as pg_dumpall will be easiest I think too.
Thanks Deepak
From: Devrim Gündüz <devrim@gunduz.org>
Sent: Sunday, December 8, 2024 2:14:06 AM
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>; vrms <vrms@netcologne.de>
Subject: Re: Postgres compatibility with RHEL
Sorry, but pg_dumpall is almost never the best way - or even good way.
On 7 December 2024 17:43:11 CET, vrms <vrms@netcologne.de> wrote:
I believe the best way would be to
1. setup a new rhel9 server with pg16
2. get a dump (pg_dumpall) from the old machine onto the new machine
3. restore that dump
4. copy pg_hba.conf and postgresql.conf over to the new machine
4.1. make sure to keep the new postgresql.conf and adjust custom settings you may have on the old machine with making sure those settings have not changed
If you want to do this close to zero downtime, you could set up logical replication to the new pg16 machine and once that is finished switch over and promote that to be the new main.
On 04.12.24 14:03, Siddhartha Jain wrote:
Hi,
Please let me know if Postgresql 16 is compatible with RHEL 7.9 version and RHEL 9.1 version.
I need to upgrade postgres from 11.22 to 16.6 and need information for that as the OS version is going to upgrade from 7.9 to 9.1.
Also, let me know the strategies if any to upgrade both RHEL and DB.
Thanks,
Siddhartha
