Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)
Adrian Klaver <adrian.klaver@aklaver.com>
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Bala M <krishna.pgdba@gmail.com>, Greg Sabino Mullane
<htamfids@gmail.com>, chris+google@qwirx.com
Cc: pgsql-general@lists.postgresql.org
Date: 2025-10-23T15:49:34Z
Lists: pgsql-general
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 adrian.klaver@aklaver.com