Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Kevin K Biju <kevinkbiju(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait
Date: 2025-05-30 15:31:39
Message-ID: 16904dc9-48bf-4a33-adca-3ebad22957eb@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025/05/29 5:40, Kevin K Biju wrote:
> Hi Fujii,
>
> The WaitEvent sounds good to me, I will submit a separate patch for that when I find time.
>
> Kevin
>
> On Wed, May 28, 2025 at 5:06 PM Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com <mailto:masao(dot)fujii(at)oss(dot)nttdata(dot)com>> wrote:
>
>
>
> On 2025/05/27 4:43, Kevin K Biju wrote:
> > Hi Fujii,
> >
> > Thanks for the review.
>
> So unless there are any objections, I'm planning to commit
> the patch with the following commit message.

I've pushed the patch. Thanks!

Regards,

--
Fujii Masao
NTT DATA Japan Corporation

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-05-30 16:12:46 Re: Add “FOR UPDATE NOWAIT” lock details to the log.
Previous Message Fujii Masao 2025-05-30 15:28:49 Re: Add “FOR UPDATE NOWAIT” lock details to the log.