Fix numeric width_bucket() to allow its first argument to be infinite.
Tom Lane <tgl@sss.pgh.pa.us>
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
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/utils/adt/numeric.c | modified | +3 −2 |
| src/test/regress/expected/numeric.out | modified | +13 −4 |
| src/test/regress/sql/numeric.sql | modified | +5 −2 |
Discussion
- WIDTH_BUCKET inconsistency 3 messages · 2020-10-08