Content-Type: multipart/alternative;
 boundary="------------u4o6zhvTeOr57iXSX5wEMlJ5"
Message-ID: <7882d3da-3445-4c80-a766-1246e55415da@netcologne.de>
Date: Sat, 7 Dec 2024 17:43:11 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Postgres compatibility with RHEL
To: pgsql-admin@lists.postgresql.org
References: 
 <CALOSYAfZvYFYpqNgiLG=GbZK5UNakcvqE6Pm7x9mRGqsEnQ6hQ@mail.gmail.com>
Content-Language: en-US
From: vrms <vrms@netcologne.de>
In-Reply-To: 
 <CALOSYAfZvYFYpqNgiLG=GbZK5UNakcvqE6Pm7x9mRGqsEnQ6hQ@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/7882d3da-3445-4c80-a766-1246e55415da%40netcologne.de>
Precedence: bulk

This is a multi-part message in MIME format.
--------------u4o6zhvTeOr57iXSX5wEMlJ5
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

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
--------------u4o6zhvTeOr57iXSX5wEMlJ5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <font face="Helvetica, Arial, sans-serif">I believe the best way
      would be to <br>
      <br>
        1. setup a new rhel9 server with pg16<br>
    </font>  2. get a dump (pg_dumpall) from the old machine onto the
    new machine<br>
      3. restore that dump<br>
      4. copy pg_hba.conf and postgresql.conf over to the new machine<br>
      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<br>
    <br>
    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.<br>
    <br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 04.12.24 14:03, Siddhartha Jain
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CALOSYAfZvYFYpqNgiLG=GbZK5UNakcvqE6Pm7x9mRGqsEnQ6hQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="auto">Hi,
        <div dir="auto"><br>
        </div>
        <div dir="auto">Please let me know if Postgresql 16 is
          compatible with RHEL 7.9 version and RHEL 9.1 version.</div>
        <div dir="auto">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. </div>
        <div dir="auto">Also, let me know the strategies if any to
          upgrade both RHEL and DB. </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Thanks,</div>
        <div dir="auto">Siddhartha </div>
      </div>
    </blockquote>
  </body>
</html>

--------------u4o6zhvTeOr57iXSX5wEMlJ5--