aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeHashjoin.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-02-09 15:49:58 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2017-02-09 15:49:58 -0500
commit86ef376bbe1b9568fa71e76ecfd3091d522368bb (patch)
treeed6eba183bb108d1e06840aed455e21129eb28ca /src/backend/executor/nodeHashjoin.c
parent1888fad440036195c7e7a933fc17410fad8dcc3d (diff)
downloadpostgresql-86ef376bbe1b9568fa71e76ecfd3091d522368bb.tar.gz
postgresql-86ef376bbe1b9568fa71e76ecfd3091d522368bb.zip
Blind try to fix portability issue in commit 8f93bd851 et al.
The S/390 members of the buildfarm are showing failures indicating that they're having trouble with the rint() calls I added yesterday. There's no good reason for that, and I wonder if it is a compiler bug similar to the one we worked around in d9476b838. Try to fix it using the same method as before, namely to store the result of rint() back into a "double" variable rather than immediately converting to int64. (This isn't entirely waving a dead chicken, since on machines with wider-than-double float registers, the extra store forces a width conversion. I don't know if S/390 is like that, but it seems worth trying.) In passing, merge duplicate ereport() calls in float8_timestamptz(). Per buildfarm.
Diffstat (limited to 'src/backend/executor/nodeHashjoin.c')
0 files changed, 0 insertions, 0 deletions