pgsql: Further cosmetic review of hashfn_unstable.h

From: John Naylor <john(dot)naylor(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Further cosmetic review of hashfn_unstable.h
Date: 2024-02-06 07:54:28
Message-ID: E1rXGHk-004u9B-QY@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Further cosmetic review of hashfn_unstable.h

In follow-up to e97b672c8,
* Flesh out comments explaining the incremental interface
* Clarify detection of zero bytes when hashing aligned C strings

The latter was suggested and reviewed by Jeff Davis

Discussion: https://postgr.es/m/48e8f8bbe0be9c789f98776c7438244ab7a7cc63.camel%40j-davis.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/b83033c3cff556d520281aaec399e47b4f11edbe

Modified Files
--------------
src/include/common/hashfn_unstable.h | 76 +++++++++++++++++++++++-------------
1 file changed, 49 insertions(+), 27 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Ashutosh Bapat 2024-02-06 09:26:31 Re: pgsql: Add EXPLAIN (MEMORY) to report planner memory consumption
Previous Message John Naylor 2024-02-06 07:44:43 pgsql: Simplify initialization of incremental hash state