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 akH6EGLTDxZOZyMB@bdtpg
Whole thread
In response to Re: [PATCH] doc: clarify pg_stat_lock.fastpath_exceeded scope  (Michael Paquier <michael@paquier.xyz>)
Responses Re: [PATCH] doc: clarify pg_stat_lock.fastpath_exceeded scope
List pgsql-hackers
Hi,

On Mon, Jun 29, 2026 at 09:31:36AM +0900, Michael Paquier wrote:
> On Sat, Jun 27, 2026 at 11:14:16PM +0900, Tatsuya Kawata wrote:
> > 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.
> 
> I'm finding that rather acceptable.  Bertrand-san, what do you think?

Yeah. I just wonder if we should mention it does not apply to shared relation
while at it.

Regards,

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



pgsql-hackers by date:

Previous
From: JoongHyuk Shin
Date:
Subject: Re: [PATCH] Don't call ereport(ERROR) from recovery target GUC assign hooks
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] Change wait_time column of pg_stat_lock to double precision