Re: type cache cleanup improvements
От | Alexander Korotkov |
---|---|
Тема | Re: type cache cleanup improvements |
Дата | |
Msg-id | CAPpHfdvMVevMxAob4Yav9LyW2a4nrWqxUVQ8K1=Hs7EjOPQk1w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: type cache cleanup improvements (Andrei Lepikhov <lepihov@gmail.com>) |
Список | pgsql-hackers |
On Mon, Oct 21, 2024 at 8:40 AM Andrei Lepikhov <lepihov@gmail.com> wrote: > > On 21/10/2024 06:32, Dagfinn Ilmari Mannsåker wrote: > > Alexander Korotkov <aekorotkov@gmail.com> writes: > > > >> +static Oid *in_progress_list; > >> +static int in_progress_list_len; > >> +static int in_progress_list_maxlen; > > > > Is there any particular reason not to use pg_list.h for this? > Sure. The type cache lookup has to be as much optimal as possible. > Using an array and relating sequential access to it, we avoid memory > allocations and deallocations 99.9% of the time. Also, quick access to > the single element (which we will have in real life almost all of the > time) is much faster than employing list machinery. +1, List with zero elements has to be NIL. That means continuous allocations/deallocations. ------ Regards, Alexander Korotkov Supabase
В списке pgsql-hackers по дате отправления: