Re: [dynahash] do not refill the hashkey after hash_search - Mailing list pgsql-hackers

From John Naylor
Subject Re: [dynahash] do not refill the hashkey after hash_search
Date
Msg-id CANWCAZYhutXX2AvkoRbhAFXh=Nb4uLETcZsw9oydAk61z6rV3Q@mail.gmail.com
Whole thread Raw
In response to Re: [dynahash] do not refill the hashkey after hash_search  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [dynahash] do not refill the hashkey after hash_search
List pgsql-hackers
On Wed, Oct 25, 2023 at 12:21 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> John Naylor <johncnaylorls@gmail.com> writes:
> > I'd prefer just adding "Assert(hentry->event == oldn);" and declaring
> > hentry PG_USED_FOR_ASSERTS_ONLY.
>
> I'm not aware of any other places where we have Asserts checking
> that hash_search() honored its contract.  Why do we need one here?

[removing old CC]
The author pointed out here that we're not consistent in this regard:

https://www.postgresql.org/message-id/CAEG8a3KEO_Kdt2Y5hFNWMEX3DpCXi9jtZOJY-GFUEE9QLgF%2Bbw%40mail.gmail.com

...but I didn't try seeing where the balance lay. We can certainly
just remove redundant assignments.



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Guiding principle for dropping LLVM versions?
Next
From: Amit Kapila
Date:
Subject: Re: [PoC] pg_upgrade: allow to upgrade publisher node