Re: [PATCH] Fix vacuum_delay_point happening inside lock

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Rocker" <me(at)kevinrocker(dot)com>
Cc: "Neil Chen" <carpenter(dot)nail(dot)cz(at)gmail(dot)com>, "Andrey Borodin" <x4mmm(at)yandex-team(dot)ru>, "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-09 23:53:57
Message-ID: 1778838.1786319637@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Kevin Rocker" <me(at)kevinrocker(dot)com> writes:
> Just bumping the patch to v4 for CFBot and pointed 'Discussion' to the thread root. Also confirmed check-world passes.

I wonder if we could enforce (via an Assert) that vacuum_delay_point
is only called from places where an interrupt can be accepted?
We found that that wasn't practical for CHECK_FOR_INTERRUPTS itself,
but maybe we could be stricter about vacuum_delay_point placement?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-08-10 00:08:40 Re: Support for 8-byte TOAST values, round two
Previous Message Andrey Rachitskiy 2026-08-09 22:38:46 Re: [PATCH]Fix pg_xact corruption from subtransaction abort after subcommit