Re: Improve LWLock tranche name visibility across backends
| От | Nathan Bossart |
|---|---|
| Тема | Re: Improve LWLock tranche name visibility across backends |
| Дата | |
| Msg-id | aKOeMUjcv9Gozyyg@nathan обсуждение исходный текст |
| Ответ на | Re: Improve LWLock tranche name visibility across backends (Sami Imseih <samimseih@gmail.com>) |
| Ответы |
Re: Improve LWLock tranche name visibility across backends
|
| Список | pgsql-hackers |
On Mon, Aug 18, 2025 at 01:06:42PM -0500, Sami Imseih wrote: > Attached is v10, I've been staring at the latest patch for a bit, and I'm a bit concerned at how much complexity it adds. I think it's a good idea to keep a local array of tranche names indexed by tranche ID, but the code for managing the list of DSA pointers scares me. I know we were trying to avoid using dshash earlier, if for no other reason than it's perhaps not the best data structure for the job, but ISTM we'd eliminate a lot of complexity if we offloaded the shmem pieces to a dshash table (or some other shmem-based data structure we have yet to introduce, like a dslist/dsarray). WDYT? -- nathan
В списке pgsql-hackers по дате отправления: