Re: Change GUC hashtable to use simplehash?

From: "Anton A(dot) Melnikov" <a(dot)melnikov(at)postgrespro(dot)ru>
To: John Naylor <johncnaylorls(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, Ants Aasma <ants(dot)aasma(at)cybertec(dot)at>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Junwang Zhao <zhjwpku(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Gurjeet Singh <gurjeet(at)singh(dot)im>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Change GUC hashtable to use simplehash?
Date: 2025-02-13 07:48:15
Message-ID: 5ef9fb1c-2e5a-489e-85f5-ba7ac6159577@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

On 13.02.2025 09:03, John Naylor wrote:
>
> Three weeks ago, you said "Agreed that reverting seems as a preferable
> way, and here's why." I assumed that meant you tested it, so my
> mistake. I'll take a look.
>

Sorry! I was wrong not to express my thoughts clearly here.
I meant revert in a common sense. Maybe before the optimization started
at all, because there was the fastest result on short lines.
Although it is unknown how it will be in reality and it could be
worse than optimization with some fixes.

With the best regards,

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vladlen Popolitov 2025-02-13 09:01:05 PoC. The saving of the compiled jit-code in the plan cache
Previous Message Bertrand Drouvot 2025-02-13 07:48:04 Re: Proposal - Allow extensions to set a Plan Identifier