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-05-30 16:12:46
Message-ID: 8e3ec0ff-f508-46bf-bca4-eca280d38b51@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Regards,

--
Fujii Masao
NTT DATA Japan Corporation

Attachment Content-Type Size
v1-0001-Rename-log_lock_failure-GUC-to-log_lock_failures-.patch text/plain 6.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Berg 2025-05-30 16:17:45 CHECKPOINT unlogged data
Previous Message Fujii Masao 2025-05-30 15:31:39 Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait