From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nathan Bossart <nathandbossart@gmail.com>
cc: Sami Imseih <samimseih@gmail.com>,
        Bertrand Drouvot <bertranddrouvot.pg@gmail.com>,
        pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Improve LWLock tranche name visibility across backends
In-reply-to: <aHVeqtsltQyBBvAM@nathan>
References: 
 <CAA5RZ0vvED3naph8My8Szv6DL4AxOVK3eTPS0qXsaKi=bVdW2A@mail.gmail.com>
 <aG9/OKQRgPUCxmsX@ip-10-97-1-34.eu-west-3.compute.internal>
 <CAA5RZ0ui5+=Q3ouxbrjSKa1xJvOjDD2tNYfkG-UtJJNNc-4E=g@mail.gmail.com>
 <aHDYHKdEyZiV/Aob@ip-10-97-1-34.eu-west-3.compute.internal>
 <CAA5RZ0vK_EuHwGj8nWkb1UwYjDbqvj+ZyiYPYn3CRsU8uwKUsQ@mail.gmail.com>
 <aHGJBt37dg37f1bE@nathan>
 <CAA5RZ0uic7Us255mFPJSrMFH7UY-RR8YZcjBzNDzfE4gFREDGQ@mail.gmail.com>
 <aHVeqtsltQyBBvAM@nathan>
Comments: In-reply-to Nathan Bossart <nathandbossart@gmail.com>
	message dated "Mon, 14 Jul 2025 14:46:50 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <717488.1752522932.1@sss.pgh.pa.us>
Date: Mon, 14 Jul 2025 15:55:32 -0400
Message-ID: <717489.1752522932@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/717489.1752522932%40sss.pgh.pa.us>
Precedence: bulk

Nathan Bossart <nathandbossart@gmail.com> writes:
> Ah, I missed the problem with postmaster.  Could we have the first backend
> that needs to access the table be responsible for creating it and
> populating it with the built-in/requested-at-startup entries?  Also, is
> there any chance that postmaster might need to access the tranche names?

Seems quite hazardous to let the postmaster get involved with such
a data structure.  If it seems to need to, we'd better rethink
where to put the functionality that needs the access.

			regards, tom lane