Re: Change GUC hashtable to use simplehash?

From: John Naylor <johncnaylorls(at)gmail(dot)com>
To: "Anton A(dot) Melnikov" <a(dot)melnikov(at)postgrespro(dot)ru>
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-01-22 08:37:25
Message-ID: CANWCAZY6rFYeFGGoW_eCVpubQ-QNtkbuumWQts-9FU8Qtc65cQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 17, 2025 at 4:50 PM John Naylor <johncnaylorls(at)gmail(dot)com> wrote:
>
> It would be a lot more readable to revert the offending commit
> instead, since its predecessor had a much simpler bytewise loop.

This will require a backpatch to v17. I'll take care of that soon.

--
John Naylor
Amazon Web Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Japin Li 2025-01-22 08:49:11 Re: [RFC] Lock-free XLog Reservation from WAL
Previous Message Robin Dupret 2025-01-22 08:27:09 [PATCH] Fix a tiny typo in the documentation