Re: [PATCH] Fix vacuum_delay_point happening inside lock

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kevin Rocker <me(at)kevinrocker(dot)com>, 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-10 05:31:50
Message-ID: 9498CDDE-E9A3-430B-B705-065888CA5938@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 10 Aug 2026, at 04:53, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> I wonder if we could enforce (via an Assert) that vacuum_delay_point
> is only called from places where an interrupt can be accepted?

I'd say even sleeping with LWLock is not a very good idea.

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tender Wang 2026-08-10 05:34:33 Re: RANGE partition pruning can still exclude the default partition
Previous Message Peter Smith 2026-08-10 05:30:16 Re: PSQL - improve tab completion for pub/sub options