Re: [PATCH] doc: clarify pg_stat_lock.fastpath_exceeded scope

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Cc: Tatsuya Kawata <kawatatatsuya0913@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-06-23T06:42:02Z
Lists: pgsql-hackers
On Tue, Jun 23, 2026 at 04:07:39AM +0000, Bertrand Drouvot wrote:
> 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.

Hmm.  system-views.sgml has a large paragraph about fast-path locks,
and seems to be the only location in the official docs where the term
is used.  I am wondering if the paragraph in view-pg-locks could be
improved and/or shortened with what you are proposing here, even if
most of it points to the inconsistencies one could get when querying
pg_locks due to the volatile nature of fast-path locks...  At least a
link on the pg_locks page pointing to this new section could be
something to consider.
--
Michael

Commits

  1. doc: Add new section describing fast-path locking