Re: domain for WITHOUT OVERLAPS
Paul A Jungwirth <pj@illuminatedcomputing.com>
From: Paul A Jungwirth <pj@illuminatedcomputing.com>
To: jian he <jian.universality@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-03-10T16:31:58Z
Lists: pgsql-hackers
Attachments
- v5-0001-Add-support-for-domain-types-in-WITHOUT-OVERLAPS.patch (application/octet-stream) patch v5-0001
On Tue, Mar 10, 2026 at 12:42 AM jian he <jian.universality@gmail.com> wrote:
>
> Hi.
>
> V4 looks good to me.
Thanks for taking a look!
> One minor question regarding comments in transformIndexConstraint:
> /*
> * The WITHOUT OVERLAPS part (if any) must be a range or
> * multirange type.
> */
>
> Should we change it to:
>
> /*
> * The WITHOUT OVERLAPS part (if any) base type must be a range or
> * multirange type.
> */
Sure. Here is an updated patch. It has some comment adjustments based
on Kirill's feedback too.
Yours,
--
Paul ~{:-)
pj@illuminatedcomputing.com
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix WITHOUT OVERLAPS' interaction with domains.
- 4edd6036d69c 19 (unreleased) landed
- 49f3cb453b9b 18.4 landed