Fix daterange canonicalization for +/- infinity.
authorJeff Davis <jdavis@postgresql.org>
Fri, 19 Jul 2019 00:01:44 +0000 (17:01 -0700)
committerJeff Davis <jdavis@postgresql.org>
Fri, 19 Jul 2019 00:01:44 +0000 (17:01 -0700)
commit2be355498eafaddc1c274f05884e1ed79b671655
tree27615c17d49e1d7baa847289a06e9f69ce41d930
parent8474656d993497c42caa68342c39d608f8854f8d
Fix daterange canonicalization for +/- infinity.

The values 'infinity' and '-infinity' are a part of the DATE type
itself, so a bound of the date 'infinity' is not the same as an
unbounded/infinite range. However, it is still wrong to try to
canonicalize such values, because adding or subtracting one has no
effect. Fix by treating 'infinity' and '-infinity' the same as
unbounded ranges for the purposes of canonicalization (but not other
purposes).

Backpatch to all versions because it is inconsistent with the
documented behavior. Note that this could be an incompatibility for
applications relying on the behavior contrary to the documentation.

Author: Laurenz Albe
Reviewed-by: Thomas Munro
Discussion: http://postgr.es/m/77f24ea19ab802bc9bc60ddbb8977ee2d646aec1.camel%40cybertec.at
Backpatch-through: 9.4
src/backend/utils/adt/rangetypes.c
src/test/regress/expected/rangetypes.out
src/test/regress/sql/rangetypes.sql