Re: Using POPCNT and other advanced bit manipulation instructions

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Subject: Re: Using POPCNT and other advanced bit manipulation instructions
Date: 2019-02-13 20:59:04
Message-ID: 20190213205904.GA13925@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-Feb-13, Andrew Gierth wrote:

> >>>>> "Alvaro" == Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>
> Alvaro> I've pushed this now. Let's see what the buildfarm has to say
> Alvaro> about it.
>
> Lapwing's latest failure looks like yours rather than mine now? (the
> previous two were mine)

It definitely is ... plans have changed from using IndexOnly scans to
Seqscans, which is likely fallout from the visibilitymap_count() change.
Looking.

(I patched the Makefile to add -mpopcnt to all the compile lines rather
than just the frontend one, but I can't see that explaining the
failure.)

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Gierth 2019-02-13 21:12:30 Re: Using POPCNT and other advanced bit manipulation instructions
Previous Message Thomas Munro 2019-02-13 20:52:33 Re: subscriptionCheck failures on nightjar