Re: Improve LWLock tranche name visibility across backends

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Sami Imseih <samimseih(at)gmail(dot)com>
Cc: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Rahila Syed <rahilasyed90(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improve LWLock tranche name visibility across backends
Date: 2025-08-30 02:51:38
Message-ID: aLJnOnTFSweb2pud@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I've committed the DSM registry changes. I apologize for the lackluster
commit message. My attempts at including all the details ended up being
super wordy and hard to read, so I decided to keep it terse and leave out
some of the context.

I've also attached a rebased patch that addresses all the latest feedback.
A reworked verison of the test patch is also included, but that's mostly
intended for CI purposes and is still not intended for commit (yet).

--
nathan

Attachment Content-Type Size
v19-0001-Move-dynamically-allocated-tranche-names-to-shar.patch text/plain 23.6 KB
v19-0002-Tests-for-LWLock-tranche-registration-improvemen.patch text/plain 14.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Xuneng Zhou 2025-08-30 04:02:49 Re: aio/README.md comments
Previous Message Alexandra Wang 2025-08-30 00:53:06 Re: SQL:2023 JSON simplified accessor support