INT4RANGE Upper bound always includes a higher number

From: PG Doc comments form <noreply(at)postgresql(dot)org>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Cc: themyth(dot)cs(at)gmail(dot)com
Subject: INT4RANGE Upper bound always includes a higher number
Date: 2023-10-03 19:00:49
Message-ID: 169635964997.3727336.14464470245213767871@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/16/rangetypes.html
Description:

Hi,
First I just wanted to say, the documentation is overall excellent, it has
been such a pleasure learning postgres.
In the RANGE types where it says the square bracket indicates upper bound
inclusive ],
But the issue with this is when I do upper bound inclusive it always goes
one number above.
This is contrary to your documentation says and it is also counter
intuitive.
According to your example (copied from your docs):

-- includes 3, does not include 7, and does include all points in between
SELECT '[3,7)'::int4range;

But this is not true, it shows 3 and 7

And if i do:
SELECT '(3,7]'::INT4RANGE;
It shows:

[4,8)
(1 row)

Please can someone explain ?

Thank you

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2023-10-03 19:25:19 Corresponding documentation page does not mention about `spread` mode
Previous Message Laurenz Albe 2023-10-03 13:46:23 Re: unnest multirange, returned order