public inbox for [email protected]
help / color / mirror / Atom feedFrom: vrms <[email protected]>
To: [email protected]
Subject: Re: Postgres compatibility with RHEL
Date: Sat, 7 Dec 2024 17:43:11 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CALOSYAfZvYFYpqNgiLG=GbZK5UNakcvqE6Pm7x9mRGqsEnQ6hQ@mail.gmail.com>
References: <CALOSYAfZvYFYpqNgiLG=GbZK5UNakcvqE6Pm7x9mRGqsEnQ6hQ@mail.gmail.com>
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
view thread (7+ messages) latest in thread
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]
Subject: Re: Postgres compatibility with RHEL
In-Reply-To: <[email protected]>
* 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