Re: GIN index isn’t working with intarray

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Maeldron T(dot)" <maeldron(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: GIN index isn’t working with intarray
Date: 2015-12-21 23:15:36
Message-ID: 14840.1450739736@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Maeldron T." <maeldron(at)gmail(dot)com> writes:
> As soon as intarray is created, the &&, @>, <@ operators
> stop using the GIN index.

intarray defines its own versions of those operators, which have nothing
to do with the standard GIN index. You can create an index using
intarray's custom GIN opclass, instead.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2015-12-21 23:27:55 Re: BUG #13666: REASSIGN OWNED BY doesn't affect the relation underlying composite type
Previous Message Alvaro Herrera 2015-12-21 22:54:50 Re: BUG #9923: "reassign owned" does not change permissions grantor