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

From: Tatsuya Kawata <kawatatatsuya0913(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] doc: clarify pg_stat_lock.fastpath_exceeded scope
Date: 2026-06-20 09:14:59
Message-ID: CAHza6qc_L-8qnT6Y2jzT+4GPR2WEMtD2GMjNe9YtTAECJRL9Fw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Bertrand-san, Michael-san,

Thanks for the feedback. Centralizing the explanation and linking
from views makes sense, so v2 takes that approach.

Specifically, v2:

* Adds a new "Fast-Path Locking" subsection under Explicit Locking
(13.3.1.1, inside Table-Level Locks).

* References the new section from:
- pg_stat_lock.fastpath_exceeded (monitoring.sgml)
- pg_locks.fastpath (system-views.sgml)
- max_locks_per_transaction (config.sgml)

Patch v2 attached.

Regards,
Tatsuya Kawata

Attachment Content-Type Size
v2-0001-doc-add-Fast-Path-Locking-section.patch application/octet-stream 4.6 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Riou 2026-06-20 09:18:01 Re: PROXY protocol support
Previous Message Florents Tselai 2026-06-20 08:34:57 Re: More jsonpath methods: translate, split, join