Re: [PATCH] Fix vacuum_delay_point happening inside lock

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Neil Chen <carpenter(dot)nail(dot)cz(at)gmail(dot)com>
Cc: Kevin Rocker <me(at)kevinrocker(dot)com>, pgsql-hackers mailing list <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Fix vacuum_delay_point happening inside lock
Date: 2026-08-04 10:03:13
Message-ID: 623751C6-7521-4E17-9747-721930864A69@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 4 Aug 2026, at 13:13, Neil Chen <carpenter(dot)nail(dot)cz(at)gmail(dot)com> wrote:
>
> Assert(InterruptHoldoffCount == 0);
> Assert(CritSectionCount == 0);
>
> With assistance from OpenAI Codex (Sol), I tried this locally; it builds and
> passes the core regression tests. I have not benchmarked the performance
> tradeoff described above.

I think that asserts are a bit too much. I observed several other
non-interruptible cases of check for interrupts. But all other cases
that I found were called sometimes without LWlocks too.

Also, make check-world is completely different beast than make check.
I will take a lot more time, but also cover a lot more cases. I used
regression tests, isolation and some subset of other tests. With Sol,
perhaps, you can scan through logs of whole make check-world.

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2026-08-04 10:07:55 RE: CREATE SUBSCRIPTION ... SERVER vs. pg_dump, etc.
Previous Message Daniel Gustafsson 2026-08-04 10:02:43 Re: data_checksums + debug_discard_caches = crash