From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, 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:50:39 |
Message-ID: | 20210609005039.GW16435@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2021-06-09 01:37:53 | Re: Misplaced superuser check in pg_log_backend_memory_contexts() |
Previous Message | Peter Geoghegan | 2021-06-09 00:47:28 | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |