Re: Using POPCNT and other advanced bit manipulation instructions

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
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 21:12:30
Message-ID: 871s4bo0vr.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>>>> "Alvaro" == Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:

>> Lapwing's latest failure looks like yours rather than mine now? (the
>> previous two were mine)

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

As for the rest, crake's "configure" failure was due to Andrew aborting
a run presumably to tweak the config, and fulmar finished a run just
before I committed the fix that should turn it green again. I'm
obviously going to keep watching, but to my knowledge only crake
(x-version test) and lorikeet (cygwin) should still be broken from my
stuff.

--
Andrew (irc:RhodiumToad)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-02-13 21:38:35 Re: Proposed refactoring of planner header files
Previous Message Alvaro Herrera 2019-02-13 20:59:04 Re: Using POPCNT and other advanced bit manipulation instructions