Re: domain for WITHOUT OVERLAPS

From: Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: domain for WITHOUT OVERLAPS
Date: 2026-03-10 16:33:18
Message-ID: CA+renyV3a+nXntdUBoG++0NuPOVexVKOCC3Pe=cfTdhj9+0PdA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 10, 2026 at 2:53 AM Kirill Reshke <reshkekirill(at)gmail(dot)com> wrote:
>
> Hi!
> I v4, test comments says we check for unique violation, while test
> output says its exclusion constraint:
>
> +INSERT INTO temporal_mltrng4 VALUES ('[1,2)', '{[1,13)}'), ('[1,2)',
> '{[2,13)}'); -- not unique
> +ERROR: conflicting key value violates exclusion constraint
> "temporal_mltrng4_pk"
>
> Maybe we can update wording to be more precise? Like `-- overlaps with
> other tuple`.
>
> Other that this nit, patch looks good.

Thanks for taking a look! I changed places we say `-- not unique` to
now say `-- overlaps`. v5 is attached to my reply to jian he.

Yours,

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-03-10 16:37:15 Re: Add starelid, attnum to pg_stats and leverage this in pg_dump
Previous Message Jacob Champion 2026-03-10 16:32:30 Re: [oauth] Stabilize the libpq-oauth ABI (and allow alternative implementations?)