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

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: n(dot)bartek3762(at)gmail(dot)com
Subject: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
Date: 2025-10-29 09:54:24
Message-ID: 19098-7f8deb5093c13da2@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 19098
Logged by: Bartłomiej Nowak
Email address: n(dot)bartek3762(at)gmail(dot)com
PostgreSQL version: 18.0
Operating system: Linux pop-os x86_64
Description:

Using unique constraint, at Postgres 18, I am able to use `WITHOUT OVERLAPS`
using that, in fact I created index, that I can see at pg_indexes:
`CREATE UNIQUE INDEX inventoryoffer_unique_index ON public.test_table USING
gist (inventory_id, account_id, from_offer_id, for_account_id,
_availability_range);`
It says, that it is gist UNIQUE index.
But if I would like to just create index like that (copy and paste that
definition from pg_indexes)
I am getting error:
[0A000] ERROR: access method "gist" does not support unique indexes
which sounds weird, in fact of `WITHOUT OVERLAPS` existence

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Laurenz Albe 2025-10-29 11:31:13 Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
Previous Message Richard Guo 2025-10-29 06:45:09 Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results