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

From: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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-29 04:52:32
Message-ID: akH6EGLTDxZOZyMB@bdtpg
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-06-29 04:52:54 Re: [PATCH] Change wait_time column of pg_stat_lock to double precision
Previous Message JoongHyuk Shin 2026-06-29 04:45:37 Re: [PATCH] Don't call ereport(ERROR) from recovery target GUC assign hooks