Re: pgsql: Introduce hash_search_with_hash_value() function

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Introduce hash_search_with_hash_value() function
Date: 2024-08-15 21:01:59
Message-ID: Zr5sx2FnIoQsI6X4@nathan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Wed, Aug 07, 2024 at 02:01:30PM -0400, Robert Haas wrote:
> Also, for the notes to be useful, we'd probably need some conventions
> about how we, as a project, want to use them. If everyone does
> something different, the result isn't likely to be all that great.

What did you have in mind? Would it be sufficient to propose a template
that, once ratified, would be available in the committing checklist [0]?

[0] https://wiki.postgresql.org/wiki/Committing_checklist

--
nathan

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alexander Korotkov 2024-08-15 21:19:07 pgsql: Fix GetStrictOldestNonRemovableTransactionId() on standby
Previous Message Nathan Bossart 2024-08-15 20:49:08 pgsql: Remove dependence on -fwrapv semantics in a few places.

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Jones 2024-08-15 21:02:23 Re: [PoC] XMLCast (SQL/XML X025)
Previous Message Alena Rybakina 2024-08-15 20:58:25 Re: Showing primitive index scan count in EXPLAIN ANALYZE (for skip scan and SAOP scans)