| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |
| Date: | 2021-06-10 17:42:47 |
| Message-ID: | CAH2-WzkMMLSwoD3Nkc71yf3incJi9KjJLHSJ-W4z4NDLXnxqZQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 10, 2021 at 10:29 AM Matthias van de Meent
<boekewurm+postgres(at)gmail(dot)com> wrote:
> I see one exit for HEAPTUPLE_DEAD on a potentially recently committed
> xvac (?), and we might also check against recently committed
> transactions if xmin == xmax, although apparently that is not
> implemented right now.
I don't follow. Perhaps you can produce a test case?
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Gibson (DB Administrator) | 2021-06-10 17:43:13 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Previous Message | Robert Haas | 2021-06-10 17:29:34 | Re: [bug?] Missed parallel safety checks, and wrong parallel safety |