| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |
| Date: | 2021-06-09 00:11:20 |
| Message-ID: | 1254746.1623197480@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Geoghegan <pg(at)bowt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-06-09 00:18:18 | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |
| Previous Message | Justin Pryzby | 2021-06-09 00:10:00 | Re: array_cat anycompatible change is breaking xversion upgrade tests (v14 release notes) |