Re: GIN indexed unique constraint? - Mailing list pgsql-general

From Allan Kamau
Subject Re: GIN indexed unique constraint?
Date
Msg-id CAF3N6oTLtaveVewwYHZky6Mvd+5+TOLjzg1vFq1CSOx4zF09RA@mail.gmail.com
Whole thread Raw
In response to Re: GIN indexed unique constraint?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general


On Sun, Jun 27, 2021 at 9:41 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Sun, Jun 27, 2021 at 11:18 AM Allan Kamau <kamauallan@gmail.com> wrote:
>> Is it possible to declare a UNIQUE constraint that uses GIN indexing?

> Doesn't seem to be possible.  The btree_gin extension would provide the
> necessary code but it states explicitly that:
> "... and they lack one major feature of the standard B-tree code: the
> ability to enforce uniqueness."

GIN stores all the component elements of its input values separately.
It'd be tremendously hard even to identify which inputs share exactly
the same component elements; let alone whether inputs sharing the
same elements should be considered "equal".  For example, ARRAY[1,2]
and ARRAY[2,1] would give rise to identical sets of index entries in
a GIN array_ops index.

In short, no, this isn't something you do with a GIN index.

                        regards, tom lane

Thank you David and Tom for your speedy and informative responses.

Allan.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: GIN indexed unique constraint?
Next
From: Ray O'Donnell
Date:
Subject: Overlapping timestamptz ranges with priority