From: | Eugen Konkov <kes-kes(at)yandex(dot)ru> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Why 'infinity' is not in range '[2019-01-02, infinity]'? |
Date: | 2019-10-26 13:15:29 |
Message-ID: | 376945611.20191026161529@yandex.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Today I got next ambiguous:
select tstzrange( 'infinity', null );
tstzrange
-------------
[infinity,)
(1 row)
[DOC](https://www.postgresql.org/docs/12/rangetypes.html) stated:
>if the upper bound of the range is omitted, then all points greater than the lower bound are included in the range.
>This is equivalent to considering that the upper bound is “plus infinity”, respectively.
Thus I can write, can not?
select tstzrange( 'infinity', 'infinity' );
tstzrange
-------------
empty
(1 row)
But thus it is not not equivalent.
>But note that these infinite values are never values of the range's element type, and can never be part of the range
Thus if 'infinite values are never values of the range' then
“infinity” can not be just another value of any range type
This conclusion contradicts next doc paragraph:
>Also, some element types have a notion of “infinity”, but that is just another value so far as the range type mechanisms are concerned.
errr... mechanism of date ranges violates basic rules for 'Infinite
(Unbounded) Ranges'?
--
Best regards,
Eugen Konkov
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2019-10-26 17:48:33 | Duplicating Records When Inserting |
Previous Message | PG Doc comments form | 2019-10-25 21:56:47 | Correction For PostgreSQL Manual |