| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:44:15 |
| Message-ID: | CAH2-WznW_tfJvVG_Unin68QJWF+aHdLE=6iUzfLZOAwdjJNdCw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
I'm going to see Andres in person in 20 minutes time (for the first
time in over a year!). I'll discuss this issue with him.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-06-09 00:47:28 | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |
| Previous Message | Jeff Davis | 2021-06-09 00:33:31 | Re: alter table set TABLE ACCESS METHOD |