Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication)

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Bala M <krishna(dot)pgdba(at)gmail(dot)com>
Cc: Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Francisco Olarte <folarte(at)peoplecall(dot)com>, chris+google(at)qwirx(dot)com, 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-11-08 16:34:25
Message-ID: 65d15f90-9675-4cad-999a-cbd46da7cb38@aklaver.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/6/25 16:30, Bala M wrote:
> *
> *
> *1) Show how you have set up the publishers and subscribers.*
>
> We have configured logical replication between PostgreSQL 11 (publisher)
> and PostgreSQL 16 (subscriber).
>
> Publisher: PostgreSQL 11 with wal_level=logical,
> max_replication_slots=20, and publication created for all tables (FOR
> ALL TABLES).
>

I have not worked with a database of this size, still I would think FOR
ALL TABLES is not the way to go. That it along with the existing
activity on the publisher would result in a slow transfer of data.

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message jian he 2025-11-10 00:53:02 Re: Emitting JSON to file using COPY TO
Previous Message Bruce Momjian 2025-11-08 03:25:41 Re: Enquiry about TDE with PgSQL