From: Michael Paquier <michael@paquier.xyz>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Nathan Bossart <nathan@postgresql.org>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Move named LWLock tranche requests to shared memory.
Date: Thu, 18 Sep 2025 08:49:20 +0900
Message-ID: <aMtJAMRgeH3-YQPb@paquier.xyz> (raw)
In-Reply-To: <aMrG8F-NkiedEugc@nathan>
References: <E1uwodL-000EuJ-2j@gemulon.postgresql.org>
<aMoejB3iTWy1SxfF@paquier.xyz>
<aMoqphZNkFJ_iy_K@nathan>
<aMo0uqvCDEYmYMQD@nathan>
<aMo9V5A7S30mwCcR@paquier.xyz>
<aMrG8F-NkiedEugc@nathan>
On Wed, Sep 17, 2025 at 09:34:24AM -0500, Nathan Bossart wrote:
> Yeah, this stuff is rather precarious, and I'm a bit surprised there
> haven't been more problems in this area.
LWLock handling is quite special, but I am also getting suspicious
about some more shmem areas. Perhaps these deserve a second look,
even if the lwlock handling with its allocation of tranches is kind of
a special treatment.
Anyway, your comment additions in v3 look fine from here.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: michael@paquier.xyz, nathandbossart@gmail.com, nathan@postgresql.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Move named LWLock tranche requests to shared memory.
In-Reply-To: <aMtJAMRgeH3-YQPb@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox