]> granicus.if.org Git - postgresql/commit
Fix daterange canonicalization for +/- infinity.
authorJeff Davis <jdavis@postgresql.org>
Thu, 18 Jul 2019 23:49:10 +0000 (16:49 -0700)
committerJeff Davis <jdavis@postgresql.org>
Thu, 18 Jul 2019 23:49:10 +0000 (16:49 -0700)
commit955089d4d74d0dbaaa6c1e3a4652e96b6d1c2f54
tree0efbdc0260560d1b78713617b4054b7e5e0e9aef
parent53256e892e6bf747d4ad0250b6a803a294d3bc0e
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: https://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