Re: Change GUC hashtable to use simplehash?

Anton A. Melnikov <a.melnikov@postgrespro.ru>

From: "Anton A. Melnikov" <a.melnikov@postgrespro.ru>

To: John Naylor <johncnaylorls@gmail.com>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Jeff Davis <pgsql@j-davis.com>, Ants Aasma <ants.aasma@cybertec.at>, Heikki Linnakangas <hlinnaka@iki.fi>, Junwang Zhao <zhjwpku@gmail.com>, jian he <jian.universality@gmail.com>, Andres Freund <andres@anarazel.de>, Gurjeet Singh <gurjeet@singh.im>, pgsql-hackers@postgresql.org

Date: 2025-02-25T07:18:29Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Silence warning in older versions of Valgrind
- fde7c0164ea2 17.5 landed
- 0600d276d485 18.0 landed
Revert "Speed up tail processing when hashing aligned C strings, take two"
- 6555fe197914 17.3 landed
- 235328ee4ae4 18.0 landed
Speed up tail processing when hashing aligned C strings, take two
- a365d9e2e8c1 17.0 landed
Teach fasthash_accum to use platform endianness for bytewise loads
- 0c25fee35903 17.0 landed
Add macro to disable address safety instrumentation
- db17594ad73a 17.0 landed
Convert uses of hash_string_pointer to fasthash equivalent
- f956ecd0353b 17.0 landed
Speed up tail processing when hashing aligned C strings
- 07f0f6abfc7f 17.0 landed
Add helper functions for dshash tables with string keys.
- 42a1de3013ea 17.0 cited
Fix warnings in cpluspluscheck
- 257998508672 17.0 landed
Further cosmetic review of hashfn_unstable.h
- b83033c3cff5 17.0 landed
Simplify initialization of incremental hash state
- 9ed3ee5001b6 17.0 landed
Add optimized C string hashing
- 0aba2554409e 17.0 landed
Add inline incremental hash functions for in-memory use
- e97b672c88f6 17.0 landed
Make all Perl warnings fatal
- c5385929593d 17.0 cited

On 25.02.2025 06:55, John Naylor wrote:
> On Sat, Feb 15, 2025 at 12:28 PM John Naylor <johncnaylorls@gmail.com> wrote:
>>
>> On Fri, Feb 14, 2025 at 6:40 PM Anton A. Melnikov
>> <a.melnikov@postgrespro.ru> wrote:
>>> Yes, of course. I tested this patch on the current master at 9e17ac997
>>> in the same way and found no valgrind errors.
>>
>> Thanks, I'll push next week after the next minor release.
> 
> Committed.
> 

Thanks!

With the best wishes,

-- 
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company