pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Anton A. Melnikov <a.melnikov@postgrespro.ru>
To: John Naylor <johncnaylorls@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jeff Davis <pgsql@j-davis.com>
Cc: Ants Aasma <ants.aasma@cybertec.at>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Junwang Zhao <zhjwpku@gmail.com>
Cc: jian he <jian.universality@gmail.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Gurjeet Singh <gurjeet@singh.im>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Change GUC hashtable to use simplehash?
Date: Thu, 13 Feb 2025 10:48:15 +0300
Message-ID: <5ef9fb1c-2e5a-489e-85f5-ba7ac6159577@postgrespro.ru> (raw)
In-Reply-To: <CANWCAZbxVto_L6ynXd4rPNyDbXoJxCTJJQV6zkfFriHEcP-Vxw@mail.gmail.com>
References: <c95e1821b6a69ec0c40eb0252e037b68a62cdae3.camel@j-davis.com>
	<2b0df3af97fac73a40aba16a58837e2cee594b1f.camel@j-davis.com>
	<CANWCAZYLvWOm-1XLT8wGoXGgNBEV_NPMWJY4gM6cXa7LHVDjtw@mail.gmail.com>
	<a3a959f6-14b8-4819-ac04-eaf2aa2e868d@postgrespro.ru>
	<CANWCAZZ0ptKxEyO504OjZOr3Co=WaSEQG5eUU-TFmqD4twhe_w@mail.gmail.com>
	<0647027b-9c9a-4f16-8f7c-3f9f3eb9451e@postgrespro.ru>
	<1520769.1736991361@sss.pgh.pa.us>
	<16198d33-a4e2-46db-b6c3-494367f5816d@postgrespro.ru>
	<CANWCAZbg_pN72nwaeq5pyBOV__Cbs2=HoUPh8NJW3LuF48JkQw@mail.gmail.com>
	<CANWCAZY6rFYeFGGoW_eCVpubQ-QNtkbuumWQts-9FU8Qtc65cQ@mail.gmail.com>
	<4c739718-27d6-44fe-9113-56a251c13275@postgrespro.ru>
	<CANWCAZai=YQNV_VY6tt=pL2RquU2NNr2WQbuj3G8hYeJBeGyyA@mail.gmail.com>
	<f3aa2d45-3b28-41c5-9499-a1bc30e0f8ec@postgrespro.ru>
	<CANWCAZZJ0NqpsW27n3xArpStNhhq1qv6KO3v_mBc8vnxE0WHMw@mail.gmail.com>
	<42304488-65ce-4604-854e-2aaf3bc8f09d@postgrespro.ru>
	<CANWCAZbxVto_L6ynXd4rPNyDbXoJxCTJJQV6zkfFriHEcP-Vxw@mail.gmail.com>

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





view thread (103+ messages)  latest in thread

Message-ID: <5ef9fb1c-2e5a-489e-85f5-ba7ac6159577@postgrespro.ru>
Permalink:  ../5ef9fb1c-2e5a-489e-85f5-ba7ac6159577@postgrespro.ru/
Also on:    postgresql.org/message-id/5ef9fb1c-2e5a-489e-85f5-ba7ac6159577@postgrespro.ru

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-hackers@postgresql.org
  Cc: a.melnikov@postgrespro.ru, johncnaylorls@gmail.com, tgl@sss.pgh.pa.us, pgsql@j-davis.com, ants.aasma@cybertec.at, hlinnaka@iki.fi, zhjwpku@gmail.com, jian.universality@gmail.com, andres@anarazel.de, gurjeet@singh.im
  Subject: Re: Change GUC hashtable to use simplehash?
  In-Reply-To: <5ef9fb1c-2e5a-489e-85f5-ba7ac6159577@postgrespro.ru>
  References: <c95e1821b6a69ec0c40eb0252e037b68a62cdae3.camel@j-davis.com> <CANWCAZYLvWOm-1XLT8wGoXGgNBEV_NPMWJY4gM6cXa7LHVDjtw@mail.gmail.com> <a3a959f6-14b8-4819-ac04-eaf2aa2e868d@postgrespro.ru> <CANWCAZZ0ptKxEyO504OjZOr3Co=WaSEQG5eUU-TFmqD4twhe_w@mail.gmail.com> <0647027b-9c9a-4f16-8f7c-3f9f3eb9451e@postgrespro.ru> <1520769.1736991361@sss.pgh.pa.us> <16198d33-a4e2-46db-b6c3-494367f5816d@postgrespro.ru> <CANWCAZbg_pN72nwaeq5pyBOV__Cbs2=HoUPh8NJW3LuF48JkQw@mail.gmail.com> <CANWCAZY6rFYeFGGoW_eCVpubQ-QNtkbuumWQts-9FU8Qtc65cQ@mail.gmail.com> <4c739718-27d6-44fe-9113-56a251c13275@postgrespro.ru> <CANWCAZai=YQNV_VY6tt=pL2RquU2NNr2WQbuj3G8hYeJBeGyyA@mail.gmail.com> <f3aa2d45-3b28-41c5-9499-a1bc30e0f8ec@postgrespro.ru> <CANWCAZZJ0NqpsW27n3xArpStNhhq1qv6KO3v_mBc8vnxE0WHMw@mail.gmail.com> <42304488-65ce-4604-854e-2aaf3bc8f09d@postgrespro.ru> <CANWCAZbxVto_L6ynXd4rPNyDbXoJxCTJJQV6zkfFriHEcP-Vxw@mail.gmail.com> <5ef9fb1c-2e5a-489e-85f5-ba7ac6159577@postgrespro.ru>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox