MIME-Version: 1.0
References: <176338523296.768.15170481907256908191@wrigleys.postgresql.org>
In-Reply-To: <176338523296.768.15170481907256908191@wrigleys.postgresql.org>
From: Paul A Jungwirth <pj@illuminatedcomputing.com>
Date: Mon, 17 Nov 2025 09:06:58 -0800
Message-ID: 
 <CA+renyU-m8-tD7_Ab8Oy8+5wutLOwFnrqhYOsrchtsuLt9fvfA@mail.gmail.com>
Subject: Re: Typo in range types documentation
To: aine@deepminer.co.uk, pgsql-docs@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BrenyU-m8-tD7_Ab8Oy8%2B5wutLOwFnrqhYOsrchtsuLt9fvfA%40mail.gmail.com>
Precedence: bulk

On Mon, Nov 17, 2025 at 8:34=E2=80=AFAM PG Doc comments form
<noreply@postgresql.org> wrote:
> It looks to me as if there is an error in the sample associated with
> documentation on date ranges on page:
> https://www.postgresql.org/docs/current/rangetypes.html
> If you scroll to the last few examples on the page, the values inserted a=
re
> in [) brackets rather than [] brackets.

Do you mean the room_reservation table? A tsrange uses [) syntax,
signifying closed/open endpoints. So it includes the start time but
not the end time. This is the most common way to use ranges, since it
lets adjacent ranges "lock together" without any overlap.

You can input tsranges with whatever endpoints you like, but they will
use [) syntax when they draw themselves. You can define new range
types with different behavior though. See
https://www.postgresql.org/docs/18/rangetypes.html#RANGETYPES-DISCRETE

Yours,

--=20
Paul              ~{:-)
pj@illuminatedcomputing.com