| From: | shihao zhong <zhong950419(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | mostafa nabil <mostafa(dot)nabil(dot)nafie(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, sk(at)zsrv(dot)org, me(at)kevinrocker(dot)com |
| Subject: | Re: BUG #19628: Uninterruptible vacuum during hash index processing |
| Date: | 2026-10-03 04:05:05 |
| Message-ID: | CAGRkXqTOt7NhoLS=QLMLKBL+Bzc_MMRsJhZxi+BzFT9XZNyNsw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi Heikki,
On 02/10/2026, Heikki Linnakangas wrote:
> Do we have more places where we call vacuum_delay_point() while holding
> locks?
I tried to run tests under assertion you had and I did not see any new
failures.
I also asked Fable to list 28 use cases and manually check the code path
and did not find any vacuum_delay_point with LWLock holding.
But, there is a thread on hackers with the same three fixes, in case you
have not seen it. Kevin Rocker's v8 is here:
https://postgr.es/m/d46104e6-19e0-4dfe-bb64-8ff21d53b1dd@app.fastmail.com
Tom suggested the Assert there, and v8-0003 adds it.
Thanks,
Shihao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shihao zhong | 2026-10-03 04:12:43 | Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation |
| Previous Message | Heikki Linnakangas | 2026-10-02 21:55:25 | Re: BUG #19628: Uninterruptible vacuum during hash index processing |