Re: Change GUC hashtable to use simplehash?

From: John Naylor <johncnaylorls(at)gmail(dot)com>
To: Junwang Zhao <zhjwpku(at)gmail(dot)com>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gurjeet Singh <gurjeet(at)singh(dot)im>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Change GUC hashtable to use simplehash?
Date: 2024-01-17 07:15:11
Message-ID: CANWCAZbSFXbkSw+nOUeN0FD-pEV1Lqvc22H3QnWVhGREYMY-YA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I spent some time rewriting the comments and a couple other cosmetic
changes, and squashed into two patches: the second one has the
optimized string hashing. They each have still just one demo use case.
It looks pretty close to commitable, but I'll leave this up for a few
days in case anyone wants to have another look.

After this first step is out of the way, we can look into using this
more widely, including dynahash and the GUC hash.

Attachment Content-Type Size
v14-0002-Add-optimized-C-string-hashing.patch text/x-patch 6.8 KB
v14-0001-Add-inline-incremental-hash-functions-for-in-mem.patch text/x-patch 9.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-01-17 07:28:52 Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx
Previous Message Michael Paquier 2024-01-17 06:44:30 Re: "ERROR: could not open relation with OID 16391" error was encountered when reindexing