Re: Typo in range types documentation

From: Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com>
To: aine(at)deepminer(dot)co(dot)uk, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Typo in range types documentation
Date: 2025-11-17 17:06:58
Message-ID: CA+renyU-m8-tD7_Ab8Oy8+5wutLOwFnrqhYOsrchtsuLt9fvfA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Mon, Nov 17, 2025 at 8:34 AM PG Doc comments form
<noreply(at)postgresql(dot)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 are
> 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,

--
Paul ~{:-)
pj(at)illuminatedcomputing(dot)com

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message r314tive 2025-11-18 11:55:00 Re: Ambiguity in IS JSON description and logic
Previous Message Fujii Masao 2025-11-17 14:26:14 Re: Document default values for --fsync-interval and --plugin in pg_recvlogical