pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: n.bartek3762@gmail.com
Subject: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
Date: Wed, 29 Oct 2025 09:54:24 +0000
Message-ID: <19098-7f8deb5093c13da2@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      19098
Logged by:          Bartłomiej Nowak
Email address:      n.bartek3762@gmail.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



view thread (16+ messages)  latest in thread

Message-ID: <19098-7f8deb5093c13da2@postgresql.org>
Permalink:  ../19098-7f8deb5093c13da2@postgresql.org/
Also on:    postgresql.org/message-id/19098-7f8deb5093c13da2@postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, n.bartek3762@gmail.com
  Subject: Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
  In-Reply-To: <19098-7f8deb5093c13da2@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox