From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: move some bitmapset.c macros to bitmapset.h |
Date: | 2022-12-06 05:57:31 |
Message-ID: | 3555640.1670306251@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> Maybe there's a path of lesser resistance... There's been a bit of
> work in pg_bitutils.h to define some of the bit manipulation functions
> for size_t types which wrap the 32 or 64-bit version of the function
> accordingly. Couldn't we just define one of those for
> pg_rightmost_one_pos and then use a size_t as the bitmap word type?
It doesn't seem particularly wise to me to hard-wire the bitmap
word size as sizeof(size_t). There is not a necessary connection
between those things: there could be a performance reason to
choose a word width that's different from size_t.
If we do put RIGHTMOST_ONE functionality into pg_bitutils.h,
I'd envision it as pg_bitutils.h exporting both 32-bit and
64-bit versions of that, and then bitmapset.c choosing the
appropriate one just like it chooses bmw_rightmost_one_pos.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | John Naylor | 2022-12-06 06:21:04 | Re: move some bitmapset.c macros to bitmapset.h |
Previous Message | David Rowley | 2022-12-06 05:46:38 | Re: move some bitmapset.c macros to bitmapset.h |