aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeHashjoin.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-06-15 12:15:56 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-06-15 12:15:56 -0400
commite532b1d57df9b55557263303dba883e06521b0d2 (patch)
treebe8bfcd58718b72e78514377d006d83c00741d56 /src/backend/executor/nodeHashjoin.c
parent7a3543c2ea23d032865f207c2605942b7a32e9ba (diff)
downloadpostgresql-e532b1d57df9b55557263303dba883e06521b0d2.tar.gz
postgresql-e532b1d57df9b55557263303dba883e06521b0d2.zip
Fix power() for infinity inputs some more.
Buildfarm results for commit decbe2bfb show that AIX and illumos have non-POSIX-compliant pow() functions, as do ancient NetBSD and HPUX releases. While it's dubious how much we should care about the latter two platforms, the former two are probably enough reason to put in manual handling of infinite-input cases. Hence, do so, and clean up the post-pow() error handling to reflect its now-more-limited scope. (Notably, while we no longer expect to ever see EDOM from pow(), report it as a domain error if we do. The former coding had the net effect of expensively converting the error to ERANGE, which seems highly questionable: if pow() wanted to report ERANGE, it would have done so.) Patch by me; thanks to Michael Paquier for review. Discussion: https://postgr.es/m/E1jkU7H-00024V-NZ@gemulon.postgresql.org
Diffstat (limited to 'src/backend/executor/nodeHashjoin.c')
0 files changed, 0 insertions, 0 deletions