Re: type cache cleanup improvements - Mailing list pgsql-hackers

From Andrei Lepikhov
Subject Re: type cache cleanup improvements
Date
Msg-id f8d8d179-ad31-4b46-aaef-3916be8bc8af@gmail.com
Whole thread Raw
In response to Re: type cache cleanup improvements  (Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>)
Responses Re: type cache cleanup improvements
List pgsql-hackers
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.

-- 
regards, Andrei Lepikhov




pgsql-hackers by date:

Previous
From: Andrei Lepikhov
Date:
Subject: Re: type cache cleanup improvements
Next
From: Amit Kapila
Date:
Subject: Re: Make default subscription streaming option as Parallel