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-11 07:50:06
Message-ID: bbf4eca8-7c5b-4c9a-96e1-3f2f121a8329@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> Instead, wouldn't it be simpler to update LockAcquireExtended() to
> take a new argument, like logLockFailure, to control whether
> a lock failure should be logged directly? I’ve adjusted the patch
> accordingly and attached it. Please let me know what you think!
>
> Regards,
Thank you!

It's very simple and nice.
It seems like it can also handle other lock failure cases by extending
logLockFailure.

I agree with this propose.

Regards,

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Florents Tselai 2025-03-11 08:08:06 Re: encode/decode support for base64url
Previous Message David Rowley 2025-03-11 07:48:33 Re: Query ID Calculation Fix for DISTINCT / ORDER BY and LIMIT / OFFSET