aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-10-08 12:37:59 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-10-08 12:37:59 -0400
commit8ce423b1912b8303dbec5dc3ec78a7a725acf6c2 (patch)
tree0dd96189eec828d01611dda11c5a98712a810ffc /src/backend/access/gist/gistproc.c
parentb90b79e1409b7cbffcadf89ae2e85c7ba1332818 (diff)
downloadpostgresql-8ce423b1912b8303dbec5dc3ec78a7a725acf6c2.tar.gz
postgresql-8ce423b1912b8303dbec5dc3ec78a7a725acf6c2.zip
Fix numeric width_bucket() to allow its first argument to be infinite.
While the calculation is not well-defined if the bounds arguments are infinite, there is a perfectly sane outcome if the test operand is infinite: it's just like any other value that's before the first bucket or after the last one. width_bucket_float8() got this right, but I was too hasty about the case when adding infinities to numerics (commit a57d312a7), so that width_bucket_numeric() just rejected it. Fix that, and sync the relevant error message strings. No back-patch needed, since infinities-in-numeric haven't shipped yet. Discussion: https://postgr.es/m/2465409.1602170063@sss.pgh.pa.us
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions