Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic
Date
Msg-id 1254746.1623197480@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic
List pgsql-hackers
Peter Geoghegan <pg@bowt.ie> writes:
> On Tue, Jun 8, 2021 at 5:27 AM Matthias van de Meent
>>> (gdb) p GlobalVisCatalogRels
>>> $57 = {definitely_needed = {value = 926025113}, maybe_needed = {value = 926025112}}

>> This maybe_needed is older than the OldestXmin, which indeed gives us
>> this problematic behaviour:

> Good catch.

I wonder if this is a variant of the problem shown at

https://www.postgresql.org/message-id/2591376.1621196582%40sss.pgh.pa.us

where maybe_needed was visibly quite insane.  This value is
less visibly insane, but it's still wrong.  It might be
interesting to try running this test case with the extra
assertions I proposed there, to try to narrow down where
it's going off the rails.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: array_cat anycompatible change is breaking xversion upgrade tests (v14 release notes)
Next
From: Justin Pryzby
Date:
Subject: Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic