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

From: cca5507 <cca5507(at)qq(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Yuki Seino <seinoyu(at)oss(dot)nttdata(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add “FOR UPDATE NOWAIT” lock details to the log.
Date: 2026-05-14 05:27:58
Message-ID: tencent_7CEC9A42070A996A5F53E4659EF0CE0EF609@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

> Yes, logging every autovacuum lock failure would be too noisy.
> I was thinking that log_lock_failure should apply only to LOCK TABLE ... NOWAIT,
> but per the current code, restricting it that way seems difficult.

I wrote a simple patch to support LOCK NOWAIT only.

Looking forward to your comments!

--
Regards,
ChangAo Chen

Attachment Content-Type Size
v1-0001-Make-log_lock_failures-support-LOCK-NOWAIT.patch application/octet-stream 9.3 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-05-14 05:29:57 Re: Add pg_stat_kind_info system view
Previous Message jian he 2026-05-14 04:36:56 Re: [PATCH] Rebuild CHECK constraints after generated column SET EXPRESSION