]> granicus.if.org Git - postgresql/commit
Fix daterange canonicalization for +/- infinity.
authorJeff Davis <jdavis@postgresql.org>
Thu, 18 Jul 2019 19:42:39 +0000 (12:42 -0700)
committerJeff Davis <jdavis@postgresql.org>
Thu, 18 Jul 2019 20:41:10 +0000 (13:41 -0700)
commite6feef571a016c9dac52a01aebad484768eb5c68
treefb563ac7fce80fbf663bfa317756bad5968d40ab
parentd004147eb3ece6b5981dbdd3d918ffc3f23fc505
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