pgsql: Dodge portability issue (apparent compiler bug) in new tablesamp - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Dodge portability issue (apparent compiler bug) in new tablesamp
Date
Msg-id E1ZJ95g-0006lO-2R@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Dodge portability issue (apparent compiler bug) in new tablesample code.

Some of the older OS X critters in the buildfarm are failing regression,
with symptoms showing that a request for 100% sampling in BERNOULLI or
SYSTEM methods actually gets only around 50% of the table.  gdb revealed
that the computation of the "cutoff" number was producing 0x7FFFFFFF
rather than the expected 0x100000000.  Inspecting the assembly code,
it looks like gcc is trying to use lrint() instead of rint() and then
fumbling the conversion from long double to uint64.  This seems like a
clear compiler bug, but assigning the intermediate result into a plain
double variable works around it, so let's just do that.  (Another idea
would be to give up one bit of hash width so that we don't need to use
a uint64 cutoff, but let's see if this is enough.)

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/d9476b83808a39d9985845071bf0a150a3063b37

Modified Files
--------------
src/backend/access/tablesample/bernoulli.c |    4 +++-
src/backend/access/tablesample/system.c    |    4 +++-
2 files changed, 6 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Dodge portability issue (apparent compiler bug) in new tablesamp
Next
From: Joe Conway
Date:
Subject: pgsql: Improve markup for row_security.