Re: Remove traces of long in dynahash.c
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Chao Li <li.evan.chao@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-08-20T23:07:17Z
Lists: pgsql-hackers
On Wed, Aug 20, 2025 at 04:14:15PM +0800, Chao Li wrote: > I wonder if we can keep the same naming style to make the new > function name like next_pow2_64()? I don't think that this would be a good idea to have new routines published in pg_bitutils.h with names inconsistent with the existing one. next_pow2_long() and next_pow2_int() are now local to dynahash.c, so we don't really have to follow their naming pattern. It would be more important to me to choose a new name, rather in line with the other ones. After sleeping on it, I am not sure what to do with these routines. I don't deny that more refactoring can be done. However, all that can also happen outside the long -> int64 switch I am suggesting. Any comments from others? -- Michael
Commits
-
Remove dynahash.h
- e6da68a6e1d6 19 (unreleased) landed
-
Replace callers of dynahash.h's my_log() by equivalent in pg_bitutils.h
- b1187266e077 19 (unreleased) landed
-
Change dynahash.c and hsearch.h to use int64 instead of long
- 13b935cd5217 19 (unreleased) landed