From: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Sergey Aleynikov <sergey(dot)aleynikov(at)gmail(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Xmax precedes relation freeze threshold errors |
Date: | 2022-06-14 17:48:02 |
Message-ID: | 20220614174802.cpm66yeoddpr5rgz@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 2022-Jun-14, Sergey Aleynikov wrote:
> On Tue, Jun 14, 2022 at 7:12 PM Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> > - Maybe there's some bug in amcheck that causes it to report tuple
> > with an old xmax but which in reality are frozen? I don't think
> > this is very likely, but In order to discard this hypothesis, you'd
> > have to show the output of `heap_page_items` from the pages in
> > question, or at least give some thought to the bits in `t_infomask`.
>
> I've run verify_heapam() in a loop for a single table. Some runs it
> shows nothing (i've seen three consequent empty runs), and on each run
> it shows something - it reports different pages.
Oh, that definitely sounds like a bug in amcheck then. Please post the
output of
select * from heap_page_items(get_raw_page('the table', the_page));
for some of these pages, preferrably just around the time the errors for
these pages are shown; maybe someone can figure out which tuples cause
these errors and how to fix amcheck. It might be difficult to catch
tuples 'in the act' though.
Maybe you can script things so that amcheck is run and the output feeds
a script that runs heap_page_items.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"Digital and video cameras have this adjustment and film cameras don't for the
same reason dogs and cats lick themselves: because they can." (Ken Rockwell)
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2022-06-14 20:06:35 | Re: Xmax precedes relation freeze threshold errors |
Previous Message | Sergey Aleynikov | 2022-06-14 17:43:21 | Re: Xmax precedes relation freeze threshold errors |