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

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>, Yuki Seino <seinoyu(at)oss(dot)nttdata(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Add “FOR UPDATE NOWAIT” lock details to the log.
Date: 2025-06-03 01:05:55
Message-ID: a772ca08-8847-458e-a0cf-e6d980d6955a@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robins Tharakan 2025-06-03 01:15:51 Re: wrong query results on bf leafhopper
Previous Message Donghang Lin 2025-06-03 00:40:18 Re: bt_index_parent_check and concurrently build indexes