Re: Add “FOR UPDATE NOWAIT” lock details to the log.

Fujii Masao <masao.fujii@oss.nttdata.com>

From: Fujii Masao <masao.fujii@oss.nttdata.com>

To: Peter Eisentraut <peter@eisentraut.org>, Yuki Seino <seinoyu@oss.nttdata.com>, Jelte Fennema-Nio <postgres@jeltef.nl>

Cc: pgsql-hackers@lists.postgresql.org

Date: 2025-06-03T01:05:55Z

Lists: pgsql-hackers


On 2025/06/02 14:42, Peter Eisentraut wrote:
> On 30.05.25 18:12, Fujii Masao wrote:
>> On 2025/05/31 0:28, Fujii Masao wrote:
>>>>   Otherwise, maybe "log_lock_failures" would be better.
>>>
>>> Yes, this seems better for consistency with log_lock_waits.
>>
>> Patch attached.
> 
> This looks good to me.

I've pushed the patch. Thanks!

Regards,

-- 
Fujii Masao
NTT DATA Japan Corporation

Commits

Rename log_lock_failure GUC to log_lock_failures for consistency.
- 73bdcfab35ec 18.0 landed
Add GUC option to log lock acquisition failures.
- 6d376c3b0d1e 18.0 landed
Split ProcSleep function into JoinWaitQueue and ProcSleep
- 3c0fd64fec8e 18.0 cited