Re: [PATCH] Fix vacuum_delay_point happening inside lock

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Kevin Rocker <me(at)kevinrocker(dot)com>
Cc: Neil Chen <carpenter(dot)nail(dot)cz(at)gmail(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 05:44:53
Message-ID: 66BA6BDF-3622-42B1-B3AD-97B62B4818AD@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Kevin and Neil!

> On 3 Aug 2026, at 20:20, Kevin Rocker <me(at)kevinrocker(dot)com> wrote:
>

Looks like an interesting and useful improvement.

I've instrumenetd vacuum_delay_point() and CHECK_FOR_INTERRUPTS() with __FILE__ and
__LINE__ and found several other cases when we always check for interrupts where
we cannot actually process them. Let's make a combined patch?

There are couple of cases where I do not know what to do.

Best regards, Andrey Borodin.

Attachment Content-Type Size
v3-0001-Move-interrupt-checks-out-of-locked-regions.patch application/octet-stream 4.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2026-08-04 05:55:12 Re: Re-read subscription state after lock in AlterSubscription
Previous Message JoongHyuk Shin 2026-08-04 05:30:20 Re: Deadlock detector fails to activate on a hot standby replica