Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Bowen Shi <zxwsbg12138(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae
Date: 2024-05-28 06:38:00
Message-ID: CAH2-WzmaB_vjm7tT-S5DiEAiQJHRigsovWe9eP32W+URE7b9Ew@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, May 27, 2024 at 11:32 PM Bowen Shi <zxwsbg12138(at)gmail(dot)com> wrote:
>> If you can show more about dead_items, then it will either confirm or
>> disprove my theory about it being the same issue.
>
>
> (gdb) p *vacrel->dead_items
> $2 = {max_items = 11184809, num_items = 0, items = 0x7fa22f48d048}
> (gdb) p *vacrel->dead_items->items
> $3 = {ip_blkid = {bi_hi = 0, bi_lo = 0}, ip_posid = 1}
>
> The num_items is zero.

That is what I suspected. And so the issue you see looks exactly the
same as the one that I saw when debugging a production instance.

--
Peter Geoghegan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2024-05-28 07:47:58 BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning
Previous Message Bowen Shi 2024-05-28 06:31:54 Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae