| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Bala M <krishna(dot)pgdba(at)gmail(dot)com>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, chris+google(at)qwirx(dot)com |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication) |
| Date: | 2025-10-23 15:49:34 |
| Message-ID: | 8d340169-b500-4048-a665-0700813313a3@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| 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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2025-10-23 17:56:58 | Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication) |
| Previous Message | Greg Sabino Mullane | 2025-10-23 15:20:38 | Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication) |