| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Subject: | Re: BUG #17257: (auto)vacuum hangs within lazy_scan_prune() |
| Date: | 2021-10-29 18:17:19 |
| Message-ID: | CAH2-WznTo_nkbTAoBO2mCR5TzWBj8fEa4+k-K3x9YUYZ0AKVUQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Oct 29, 2021 at 6:30 AM Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
> I can propose the debugging patch to reproduce the issue that replaces
> the hang with the assert and modifies a pair of crash-causing test
> scripts to simplify the reproducing. (Sorry, I have no time now to prune
> down the scripts further as I have to leave for a week.)
This bug is similar to the one fixed in commit d9d8aa9b. And so I
wonder if code like GlobalVisTestFor() is missing something that it
needs for partitioned tables.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kamigishi Rei | 2021-10-29 18:36:51 | Re: BUG #17245: Index corruption involving deduplicated entries |
| Previous Message | PG Bug reporting form | 2021-10-29 18:14:56 | BUG #17258: Unexpected results in CHAR(1) data type |