| 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>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Improve LWLock tranche name visibility across backends |
| Date: | 2025-07-15 16:57:31 |
| Message-ID: | aHaIe44bAENt8JPW@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 15, 2025 at 11:52:19AM -0500, Sami Imseih wrote:
>> Another random thought: I worry that the dshash approach might be quite a
>> bit slower, and IIUC we just need to map an integer to a string. Maybe we
>> should just use a DSA for LWLockTrancheNames. IOW we'd leave it as a char**
>> but put it in shared memory.
>
> To use DSA just for this purpose, we would need to maintain an array of
> dsa_pointers that reference the string(s), right? I am not clear what you
> mean by using dsa to put the char**
I was imagining putting the array in one big DSA allocation instead of
carting around a pointer for each tranche name. (Sorry, I realize I am
hand-waving over some of the details.)
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2025-07-15 17:06:00 | Re: Improve LWLock tranche name visibility across backends |
| Previous Message | Sami Imseih | 2025-07-15 16:52:19 | Re: Improve LWLock tranche name visibility across backends |