Postgres Pro
Downloads
Home   >   mailing lists

Re: Add “FOR UPDATE NOWAIT” lock details to the log. - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Add “FOR UPDATE NOWAIT” lock details to the log.
Date
Msg-id 692300f6-ac2d-4cf4-86a6-84758e507955@oss.nttdata.com
Whole thread Raw
In response to Re: Add “FOR UPDATE NOWAIT” lock details to the log.  (Yuki Seino <seinoyu@oss.nttdata.com>)
Responses Re: Add “FOR UPDATE NOWAIT” lock details to the log.
List pgsql-hackers
Tree view 

On 2025/03/11 16:50, Yuki Seino wrote:
>>
>> Instead, wouldn't it be simpler to update LockAcquireExtended() to
>> take a new argument, like logLockFailure, to control whether
>> a lock failure should be logged directly? I’ve adjusted the patch
>> accordingly and attached it. Please let me know what you think!
>>
>> Regards,
> Thank you!
> 
> It's very simple and nice.
> It seems like it can also handle other lock failure cases by extending logLockFailure.
> > I agree with this propose.

Thanks for reviewing the patch!

I've made some minor cosmetic adjustments. The updated patch is attached.

Unless there are any objections, I'll proceed with committing it.

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
Attachment

pgsql-hackers by date:

Previous
From: Dagfinn Ilmari Mannsåker
Date:
Subject: Re: Changing the state of data checksums in a running cluster
Next
From: Peter Eisentraut
Date:
Subject: Re: Use "protocol options" name instead of "protocol extensions" everywhere