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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Tatsuya Kawata <kawatatatsuya0913(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-16 03:42:46
Message-ID: ajDGNnTQA4sbZS1K@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 15, 2026 at 02:17:18PM +0000, Bertrand Drouvot wrote:
> I think that the current documentation is lacking explanation as to what the fast
> path means as a whole. So I think that what we could do instead, is to explain
> what fast path means (maybe around pg_lock?). Then, we could reference it in
> pg_stat_lock if we feel the need.

A more centralized explanation that could then be used as a link from
the page of the view sounds like a good plan here.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2026-06-16 03:57:19 Re: Proposal: Conflict log history table for Logical Replication
Previous Message Michael Paquier 2026-06-16 03:23:46 Re: pg_restore handles extended statistics inconsistently with statistics data