Re: Improve LWLock tranche name visibility across backends
От | Nathan Bossart |
---|---|
Тема | Re: Improve LWLock tranche name visibility across backends |
Дата | |
Msg-id | aKS0auEl4UUlt7XO@nathan обсуждение исходный текст |
Ответ на | Re: Improve LWLock tranche name visibility across backends (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>) |
Ответы |
Re: Improve LWLock tranche name visibility across backends
|
Список | pgsql-hackers |
On Tue, Aug 19, 2025 at 08:09:53AM +0000, Bertrand Drouvot wrote: > On Mon, Aug 18, 2025 at 05:53:44PM -0500, Sami Imseih wrote: >> > (or some other shmem-based >> > data structure we have yet to introduce, like a dslist/dsarray). >> >> This will be an interesting API to invest time in, if there could be more >> use-cases. > > I did a quick check and I did not find current use cases: possible candidates > could be in ExecParallelHashTableAlloc(), PTIterationArray, PTEntryArray for > examples but I think they all know the final size upfront so there is no real > need for dsarray for those). > >> I think it's a separate discussion at this point. > > OTOH, that would be a valid use case to introduce this new API but I'm not sure > it's worth it given that the dshash looks good enough for our case (even if not > ideal though). IMHO it'd be okay to proceed with dshash for now. It would be pretty easy to switch to something like a "dslist" in the future. -- nathan
В списке pgsql-hackers по дате отправления: