INT4RANGE Upper bound always includes a higher number - Mailing list pgsql-docs

From PG Doc comments form
Subject INT4RANGE Upper bound always includes a higher number
Date
Msg-id 169635964997.3727336.14464470245213767871@wrigleys.postgresql.org
Whole thread Raw
Responses Re: INT4RANGE Upper bound always includes a higher number
List 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

pgsql-docs by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: unnest multirange, returned order
Next
From: PG Doc comments form
Date:
Subject: Corresponding documentation page does not mention about `spread` mode