Request a Demo
Home   >   mailing lists

Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication) - Mailing list pgsql-general

From Devrim Gündüz
Subject Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)
Date
Msg-id CF431B1B-D105-4EC1-90DF-C25999455F04@gunduz.org
Whole thread Raw
In response to Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)  (Bala M <krishna.pgdba@gmail.com>)
Responses Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)
RE: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)
List pgsql-general
Tree view
Hi,

This happens because of the glibc version differrence between RHEL X and RHEL Y. At this point you either have to rebuild all indexes (sorry!) or redo the upgrade via logical replication (if it works for your app's behaviour)


Devrim


On 22 October 2025 12:03:06 EEST, Bala M <krishna.pgdba@gmail.com> wrote:

Hi Team,

We are facing an issue related to index corruption after migrating our PostgreSQL 11 setup from RHEL 7 to RHEL 9 using streaming replication (base backup method).

After bringing up the standby on RHEL 9, we observed that certain tables are not returning results when queries use indexed scans. Upon investigation, the following check confirms index corruption:

The same indexes work fine on the RHEL 7 (primary) side. However, on the RHEL 9 replica, queries that rely on this index return zero records. 
Rebuilding the indexes  fixed the issue temporarily but we have many indexes  and our DB size is more than 10TB.

Environment details:

  • PostgreSQL Version: 11.15

  • OS on primary: RHEL 7.9

  • OS on standby: RHEL 9.6

  • Replication Type: Streaming replication (initialized using pg_basebackup)

  • Data Directory initialized from RHEL 7 base backup

Issue Summary:

  • Indexes appear and are the same size as per prod  on standby after base backup restore.

  • We are able to read  the data from the tables without index scans on standy by RHEL 9.

  • No filesystem or WAL errors observed in logs.

Could this be related to OS-level binary or page layout differences between RHEL 7 and RHEL 9 for PostgreSQL 11 binaries?
Any insights or recommended actions would be greatly appreciated.


Thanks & Regards,
krishna.


pgsql-general by date:

Previous
From: Ron Johnson
Date:
Subject: Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)
Next
From: David Rowley
Date:
Subject: Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)