public inbox for [email protected]
help / color / mirror / Atom feedFrom: Adrian Klaver <[email protected]>
To: Bala M <[email protected]>
To: Greg Sabino Mullane <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)
Date: Thu, 23 Oct 2025 08:49:34 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAJ4rSwvsRJhwfuem0vsws1WwRZPN8Ju2Nw0e0Oc2j7n=MXUhMg@mail.gmail.com>
References: <CAJ4rSwspyYBppQS701C=BVFX2yrP1JErgDCZXbC15BQh2zAS1Q@mail.gmail.com>
<CAKAnmmK47O_rYDB4iPe=K3QiqzJcCnnxCoYs_40Q1YWb=x0nDg@mail.gmail.com>
<CAJ4rSwvsRJhwfuem0vsws1WwRZPN8Ju2Nw0e0Oc2j7n=MXUhMg@mail.gmail.com>
On 10/23/25 07:51, Bala M wrote:
> Hi All,
>
> Thank you for the valuable responses regarding the *index corruption
> issue* we observed during our test migration of a *PostgreSQL 11*
> environment from *RHEL 7 to RHEL 9* using *streaming replication*.
>
> Based on the replies, I understand that.
> Suggested upgrading to a newer PostgreSQL version (e.g., v16 or v18)
> and using *logical replication* or *pg_dump/restore* for a clean
> rebuild.
I am not sure version 18 would a good choice at this time, it has just
been released and has no bug fix releases against it yet. Given the
other complications in your upgrade, OS upgrade and multi-version jump,
I don't think you want to add a brand new version to the mix. Postgres
17 on the other hand has been out a year and has had 6 bug/security
fixes. It is probably a more stable target version.
--
Adrian Klaver
[email protected]
view thread (21+ 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], [email protected], [email protected], [email protected]
Subject: Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)
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