From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: type cache cleanup improvements |
Date: | 2024-03-14 13:27:43 |
Message-ID: | 8114feb1-95a1-466b-ab21-3732334f5af7@sigaev.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> One thing that first pops out to me is that we can do the refactor of
> hash_initial_lookup() as an independent piece, without the extra paths
> introduced. But rather than returning the bucket hash and have the
> bucket number as an in/out argument of hash_initial_lookup(), there is
> an argument for reversing them: hash_search_with_hash_value() does not
> care about the bucket number.
Ok, no problem
>
>> 02-hash_seq_init_with_hash_value.v5.patch - introduces a
>> hash_seq_init_with_hash_value() method. hash_initial_lookup() is marked as
>> inline, but I suppose, modern compilers are smart enough to inline it
>> automatically.
>
> Likely so, though that does not hurt to show the intention to the
> reader.
Agree
>
> So I would like to suggest the attached patch for this first piece.
> What do you think?
I have not any objections
>
> It may also be an idea to use `git format-patch` when generating a
> series of patches. That makes for easier reviews.
Thanks, will try
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2024-03-14 13:32:04 | Re: BitmapHeapScan streaming read user and prelim refactoring |
Previous Message | Robert Treat | 2024-03-14 13:21:18 | Re: small_cleanups around login event triggers |