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

From: Yuki Seino <seinoyu(at)oss(dot)nttdata(dot)com>
To: Fujii Masao <masao(dot)fujii(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-03-21 06:21:57
Message-ID: a479740c-fe28-42f5-be83-272c0127cf86@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Pushed the patch. Thanks!

Thank you. I'm very happy !!

> Using the newly introduced mechanism, we can now easily extend
> the log_lock_failure GUC to support additional NOWAIT lock failures,
> such as LOCK TABLE ... NOWAIT, ALTER TABLE ... NOWAIT,
> ALTER MATERIALIZED VIEW ... NOWAIT, and ALTER INDEX ... NOWAIT.
>
> I've attached a patch implementing this.
That's a very good suggestion.

There is just one thing that bothers me.
ConditionalLockRelationOid() seems to be used by autovacuum as well.
Wouldn't this information be noise to the user?

Regards,

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2025-03-21 06:34:46 Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row
Previous Message Amul Sul 2025-03-21 05:58:44 Re: NOT ENFORCED constraint feature