Re: Remove traces of long in dynahash.c

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Remove traces of long in dynahash.c
Date: 2025-08-19 06:51:26
Message-ID: 25139C59-A1F6-44DD-AF94-984094D9C889@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Aug 19, 2025, at 14:24, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
>
> --
> Michael
> <0001-Replace-uses-of-long-by-uint64-in-dynahash.c-and-hse.patch>

-static long next_pow2_long(long num);
-static int next_pow2_int(long num);
+static uint64 next_pow2_uint64(uint64 num);
+static int next_pow2_int(uint64 num);

There are already pg_nextpower2_64() and pg_nextpower2_32() in pg_bitutils.h, feels like the new replacement functions are duplicate to the existing ones.

- * we no longer need to worry about registering hash_seq_search scans,
+ * we no uint64er need to worry about registering hash_seq_search scans,

Looks like a bad auto replacement: “no longer”, here “long" should be kept.

--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2025-08-19 07:03:48 Re: New commitfest app release on August 19th
Previous Message Peter Smith 2025-08-19 06:36:07 Re: [WIP]Vertical Clustered Index (columnar store extension) - take2