Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that

From: Kirill Reshke <reshkekirill(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: n(dot)bartek3762(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
Date: 2025-10-29 12:43:18
Message-ID: CALdSSPgxP30Ly=moH9LecURsA26+WjE1hXPkHNcVeponOeLwAg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, 29 Oct 2025 at 16:31, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
>
> I think I see what you mean:
>
> CREATE TABLE temp (
> id bigint NOT NULL,
> valid tstzrange NOT NULL,
> CONSTRAINT temp_pkey PRIMARY KEY (id, valid WITHOUT OVERLAPS)
> );
>
> SELECT pg_get_indexdef('temp_pkey'::regclass);
>
> pg_get_indexdef
> ----------------------------------------------------------------------
> CREATE UNIQUE INDEX temp_pkey ON laurenz.temp USING gist (id, valid)
>
> That CREATE INDEX statement won't work.
>
> Yours,
> Laurenz Albe
>
>

Yep, this is probably a valid rewording of the first email. Is it a
problem that is worth fixing?

--
Best regards,
Kirill Reshke

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Laurenz Albe 2025-10-29 13:52:38 Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
Previous Message Laurenz Albe 2025-10-29 12:09:32 Re: BUG #19097: System catalog modifications are allowed by alter