Re: Using POPCNT and other advanced bit manipulation instructions

From: Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Using POPCNT and other advanced bit manipulation instructions
Date: 2019-02-14 05:29:24
Message-ID: 7cd3ffa8-4889-1188-4baa-80ac4396be54@archidevsys.co.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 14/02/2019 11:17, Alvaro Herrera wrote:
> On 2019-Feb-13, Alvaro Herrera wrote:
>
>> It definitely is ... plans have changed from using IndexOnly scans to
>> Seqscans, which is likely fallout from the visibilitymap_count() change.
> I think the problem here is that "unsigned long" is 32 bits in this
> machine:

[...]

From my memory of reading of K&R many moons ago, it said that C only
guarantees that the lengths are such that

byte <= half word <= word <= long

But I don't recall ever seeing a long less than 32 bits!

Cheers,
Gavin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-02-14 05:46:42 Re: Using POPCNT and other advanced bit manipulation instructions
Previous Message Tom Lane 2019-02-14 05:24:50 Re: Using POPCNT and other advanced bit manipulation instructions