Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae
Date
Msg-id CAH2-WzmO-GPN8kpSCWzkq27FRk8xCBoDKJcMqVTYC+Dt8s4ZDQ@mail.gmail.com
Whole thread Raw
In response to Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae  (Andres Freund <andres@anarazel.de>)
Responses Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae
Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae
List pgsql-bugs
On Thu, May 16, 2024 at 12:38 PM Andres Freund <andres@anarazel.de> wrote:
> I'm wondering if there was index processing, due to the number of tuples. And
> if so, what type of indexes. There'd need to be something that could lead to
> new snapshots being acquired...

Did you ever see this theory of mine, about B-Tree page deletion +
recycling? See:


https://www.postgresql.org/message-id/flat/CAH2-Wz%3DzLcnZO8MqPXQLqOLY%3DCAwQhdvs5Ncg6qMb5nMAam0EA%40mail.gmail.com#d058a6d4b8c8fa7d1ff14349b3a50c3c

(And related nearby emails from me.)

It looked very much like index vacuuming was involved in some way when
I actually had the opportunity to use gdb against an affected
production instance that ran into the problem.

--
Peter Geoghegan



pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
Next
From: Tom Lane
Date:
Subject: Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption