aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/xlog.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-11-23 23:49:25 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2018-11-23 23:49:25 -0500
commit452b637d4b02e4aa09d45a34d7a048d3f70116bb (patch)
tree4b57527caa67e2c93ef4c243e10743a4bd031854 /src/backend/access/transam/xlog.c
parentcbdb8b4c0155b2d9679ecd79b886c29c2730b85d (diff)
downloadpostgresql-452b637d4b02e4aa09d45a34d7a048d3f70116bb.tar.gz
postgresql-452b637d4b02e4aa09d45a34d7a048d3f70116bb.zip
Adjust new test case for more portability.
Early returns from the buildfarm say that most critters are good with commit cbdb8b4c0, but gaur gives unexpected results with the test case involving a float8 that's one-ULP-less-than-2^63. It appears that that platform's version of rint() rounds that value up to 2^63 instead of leaving it be. This is possibly a bug, and it's also possible that no other platform anybody is using anywhere behaves likewise. Still, the point of the test is not to insist that everybody's rint() behaves exactly the same. Let's use two-ULPs-less-than-2^63 instead, which I've tested to act the same on gaur as on more modern hardware. (This is, more or less, exactly the portability issue I'd feared might arise...) Discussion: https://postgr.es/m/15519-4fc785b483201ff1@postgresql.org
Diffstat (limited to 'src/backend/access/transam/xlog.c')
0 files changed, 0 insertions, 0 deletions