| 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>, Alexander Lakhin <exclusion(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17257: (auto)vacuum hangs within lazy_scan_prune() |
| Date: | 2021-11-05 21:25:12 |
| Message-ID: | CAH2-Wz=CqbW2uVhXE6wmB5gryAPD=aqE5Yt3bfU3VDDkG4uECQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Nov 5, 2021 at 4:43 AM Matthias van de Meent
<boekewurm+postgres(at)gmail(dot)com> wrote:
> I added the attached instrumentation for checking xmin validity, which
> asserts what I believe are correct claims about the proc
> infrastructure:
This test case involves partitioning, but also pruning, which is very
particular about heap tuple headers being a certain way following
updates. I wonder if we're missing a
HeapTupleHeaderIndicatesMovedPartitions() test somewhere. Could be in
heapam/VACUUM/pruning code, or could be somewhere else.
Take a look at commit f16241bef7 to get some idea of what I mean.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias van de Meent | 2021-11-06 01:20:14 | Re: BUG #17257: (auto)vacuum hangs within lazy_scan_prune() |
| Previous Message | Alvaro Herrera | 2021-11-05 15:35:04 | Re: BUG #17126: Server crashes on dropping user while enumerating owned objects that are droppped concurrently |