Re: broken tables on hot standby after migration on PostgreSQL 16 (3x times last month)

From: Andres Freund <andres(at)anarazel(dot)de>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: broken tables on hot standby after migration on PostgreSQL 16 (3x times last month)
Date: 2024-05-21 15:28:39
Message-ID: 20240521152839.o4dom7ervjob73am@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2024-05-17 16:03:09 -0400, Peter Geoghegan wrote:
> On Fri, May 17, 2024 at 3:50 PM Andres Freund <andres(at)anarazel(dot)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.

That could also just be because of a different replay position, hence my
question about that somewhere else in the email...

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2024-05-21 15:42:19 Re: libpq compression (part 3)
Previous Message Dave Page 2024-05-21 15:24:23 Re: zlib detection in Meson on Windows broken?