Postgres Pro
Downloads
Home   >   mailing lists

Re: broken tables on hot standby after migration on PostgreSQL 16 (3x times last month) - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: broken tables on hot standby after migration on PostgreSQL 16 (3x times last month)
Date
Msg-id CAH2-WzkGE_QYm1ZF0NhR4S=c2GomUb3o7ecPCwe--Trapu898g@mail.gmail.com
Whole thread Raw
In response to Re: broken tables on hot standby after migration on PostgreSQL 16 (3x times last month)  (Andres Freund <andres@anarazel.de>)
Responses Re: broken tables on hot standby after migration on PostgreSQL 16 (3x times last month)
List pgsql-hackers
Tree view 
On Fri, May 17, 2024 at 3:50 PM Andres Freund <andres@anarazel.de> wrote:
> You're saying that the data is correctly accessible on primaries, but broken
> on standbys? Is there any difference in how the page looks like on the primary
> vs standby?

There clearly is. The relevant infomask bits are different. I didn't
examine it much closer than that, though.

--
Peter Geoghegan

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.
Next
From: Pavel Stehule
Date:
Subject: Re: broken tables on hot standby after migration on PostgreSQL 16 (3x times last month)