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

Tatsuya Kawata <kawatatatsuya0913@gmail.com>

From: Tatsuya Kawata <kawatatatsuya0913@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-06-27T14:14:16Z
Lists: pgsql-hackers

Attachments

Hi Bertrand-san, Michael-san,

Thanks for the additional review!

> 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.

Fixed.


> 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.

Thanks for the detailed thought.  I looked at that paragraph.  I was
hoping to fold the two together, but the content did not seem to
overlap, so I limited the change to adding a link as you suggested.

v4 attached.

Regards,
Tatsuya Kawata

Commits

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