Re: Improve LWLock tranche name visibility across backends
От | Sami Imseih |
---|---|
Тема | Re: Improve LWLock tranche name visibility across backends |
Дата | |
Msg-id | CAA5RZ0skN3ATpEvcFCUCiHDqvs6N95uzAo74wUSR93Bdgrq5Xg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Improve LWLock tranche name visibility across backends (Nathan Bossart <nathandbossart@gmail.com>) |
Ответы |
Re: Improve LWLock tranche name visibility across backends
|
Список | pgsql-hackers |
> On Mon, Aug 04, 2025 at 11:32:19AM -0500, Sami Imseih wrote: > > With a local hash table, I don't think it's necessary to introduce new > > code for managing > > a DSA based list of tranche names as is done in v3. We can go back to > > storing the shared > > trance names in dshash. > > > > What do you think? > > My first thought is that a per-backend hash table seems too > expensive/complicated for this. Couldn't it just be an array like we have > now? We can, but I was considering simplicity of implementation, and using a local hash table is slightly simpler. That said, since we're dealing with an append-only data structure, a hash table is probably more than we need. All we need is index-based lookup, so I’ll go with the local array to mirror the shared ( dsa ) array. -- Sami
В списке pgsql-hackers по дате отправления: