Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Matthias van de Meent <boekewurm+postgres@gmail.com>, pgsql-hackers@lists.postgresql.org, Masahiko Sawada <sawada.mshk@gmail.com>, Andres Freund <andres@anarazel.de>
Date: 2021-06-09T00:50:39Z
Lists: pgsql-hackers
On Tue, Jun 08, 2021 at 05:44:15PM -0700, Peter Geoghegan wrote: > On Tue, Jun 8, 2021 at 5:11 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > 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. > > Oh yeah. Justin didn't say anything about upgrading using pg_upgrade > (just something about upgrading the kernel). > > Did you use pg_upgrade here, Justin? Yes. The kernel upgrade was going to be my hand-waving dismissal of the issue when I saw someting waiting on a futex. (Since a few years ago Tom had to remind me about an old Linux futex bug which we hit after upgrading to v12 on a customer's server - they like to avoid maintenance at all costs). -- Justin
Commits
-
Deduplicate choice of horizon for a relation procarray.c.
- 3d0a4636aa4c 14.0 landed
- d9d8aa9bb9aa 15.0 landed
-
Use correct horizon when vacuuming catalog relations.
- 5a1e1d83022b 14.0 landed
-
Truncate line pointer array during VACUUM.
- 3c3b8a4b2689 14.0 cited
-
Remove tupgone special case from vacuumlazy.c.
- 8523492d4e34 14.0 cited
-
Refactor lazy_scan_heap() loop.
- 7ab96cf6b312 14.0 cited
-
snapshot scalability: Don't compute global horizons while building snapshots.
- dc7420c2c927 14.0 cited