Re: Change GUC hashtable to use simplehash? - Mailing list pgsql-hackers

From John Naylor
Subject Re: Change GUC hashtable to use simplehash?
Date
Msg-id CANWCAZZ0ptKxEyO504OjZOr3Co=WaSEQG5eUU-TFmqD4twhe_w@mail.gmail.com
Whole thread Raw
In response to Re: Change GUC hashtable to use simplehash?  ("Anton A. Melnikov" <a.melnikov@postgrespro.ru>)
Responses Re: Change GUC hashtable to use simplehash?
List pgsql-hackers
On Thu, Dec 19, 2024 at 7:10 AM Anton A. Melnikov
<a.melnikov@postgrespro.ru> wrote:
> Found that https://github.com/postgres/postgres/commit/0aba2554409ee3251d7558567edd114d8ed36dcc
> produces a valgrind error in initdb.

What architecture and valgrind version is this? We've been bitten
before by different results on Arm vs x86.

The offending code is not even my preferred way to handle the last
word of the string (see f4ad0021af), so if the current way is still
not valgrind-clean, I wonder if we should give up and add an
exception, since we know any garbage bits are masked off.

--
John Naylor
Amazon Web Services



pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: Can rs_cindex be < 0 for bitmap heap scans?
Next
From: Kirill Reshke
Date:
Subject: Re: log_min_messages per backend type