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

2024-05-21 Thread Andres Freund
On 2024-05-17 16:03:09 -0400, Peter Geoghegan wrote: > On Fri, May 17, 2024 at 3:50 PM Andres Freund 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? > >

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

2024-05-20 Thread Pavel Stehule
Hi > > Another question: Do you use pg_repack or such? > pg_repack was used for some tables, but I found broken tables, where pg_repack was not used. Regards Pavel > > Greetings, > > Andres Freund >

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

2024-05-17 Thread Pavel Stehule
pá 17. 5. 2024 v 22:05 odesílatel Pavel Stehule napsal: > > > pá 17. 5. 2024 v 21:50 odesílatel Andres Freund > napsal: > >> Hi, >> >> On 2024-05-17 15:12:31 +0200, Pavel Stehule wrote: >> > after migration on PostgreSQL 16 I seen 3x times (about every week) >> broken >> > tables on replica

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

2024-05-17 Thread Pavel Stehule
pá 17. 5. 2024 v 21:50 odesílatel Andres Freund napsal: > Hi, > > On 2024-05-17 15:12:31 +0200, Pavel Stehule wrote: > > after migration on PostgreSQL 16 I seen 3x times (about every week) > broken > > tables on replica nodes. The query fails with error > > Migrating from what version? > I

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

2024-05-17 Thread Peter Geoghegan
On Fri, May 17, 2024 at 3:50 PM Andres Freund 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

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

2024-05-17 Thread Andres Freund
Hi, On 2024-05-17 15:12:31 +0200, Pavel Stehule wrote: > after migration on PostgreSQL 16 I seen 3x times (about every week) broken > tables on replica nodes. The query fails with error Migrating from what version? You're saying that the data is correctly accessible on primaries, but broken on

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

2024-05-17 Thread Peter Geoghegan
On Fri, May 17, 2024 at 1:18 PM Pavel Stehule wrote: > pá 17. 5. 2024 v 18:02 odesílatel Peter Geoghegan napsal: >> You've shown an inconsistency between the primary and standby with >> respect to the heap tuple infomask bits related to freezing. It looks >> like a FREEZE WAL record from the

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

2024-05-17 Thread Pavel Stehule
pá 17. 5. 2024 v 18:02 odesílatel Peter Geoghegan napsal: > On Fri, May 17, 2024 at 9:13 AM Pavel Stehule > wrote: > > after migration on PostgreSQL 16 I seen 3x times (about every week) > broken tables on replica nodes. The query fails with error > > > > ERROR: could not access status of

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

2024-05-17 Thread Peter Geoghegan
On Fri, May 17, 2024 at 9:13 AM Pavel Stehule wrote: > after migration on PostgreSQL 16 I seen 3x times (about every week) broken > tables on replica nodes. The query fails with error > > ERROR: could not access status of transaction 1442871302 > DETAIL: Could not open file "pg_xact/0560": No