Request a Demo
Home   >   mailing lists

Re: [PATCH] doc: clarify pg_stat_lock.fastpath_exceeded scope - Mailing list pgsql-hackers

From Bertrand Drouvot
Subject Re: [PATCH] doc: clarify pg_stat_lock.fastpath_exceeded scope
Date
Msg-id ajoGi58Qlgta3lWn@bdtpg
Whole thread
In response to Re: [PATCH] doc: clarify pg_stat_lock.fastpath_exceeded scope  (Tatsuya Kawata <kawatatatsuya0913@gmail.com>)
Responses Re: [PATCH] doc: clarify pg_stat_lock.fastpath_exceeded scope
List pgsql-hackers
Tree view 
Hi Kawata-san,

On Mon, Jun 22, 2026 at 08:34:12PM +0900, Tatsuya Kawata wrote:
> Hi Bertrand-san,
> 
> Thanks for the review.
> 
> > Should we add a description of the consequences of not being able to
> > acquire the lock in fast-path (when there are no available slots)?
> > For example, we could say that this is considerably more expensive
> > and may be subject to contention.
> 
> Agreed.  v3 adds the following paragraph at the end of the Fast-Path

Thanks!

Looking closer, I'm not sure that in:

-       lock table
+       lock table.  See <xref linkend="locking-tables-fast-path"/> for
+       details.

the "for details" is needed. Looking at the pg_locks table, it looks like
"(See xxxx)" would be more consistent.

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [PATCH] Warn when io_min_workers exceeds io_max_workers
Next
From: shveta malik
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication