From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: A question on GIN indexes and arrays |
Date: | 2017-08-20 23:22:57 |
Message-ID: | CAOC+FBWU51QMFoUoPEoT7GHmiymm8VF_-Bbfj0SpAQUuLu9-Ag@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
YES!
\dx yields intarray was installed (back in the 9.1 days, maybe) and that
was clobbering the @> operator.
Looking into the implications of removing intarray now that we're at 9.6,
seems harmless, but will do my due diligence.
Thanks Jeff.
On Sun, Aug 20, 2017 at 3:15 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Sun, Aug 20, 2017 at 1:28 PM, Wells Oliver <wells(dot)oliver(at)gmail(dot)com>
> wrote:
>
>>
>> Why is this happening and what can I do to get my GIN indexes working?
>> Thanks!
>>
>>
> What extensions do you have installed in each database? I bet one of them
> (like intarray) redefines @> for one of your databases.
>
> Try fully qualifying the operator. OPERATOR(pg_catalog.@>)
>
> Cheers,
>
> Jeff
>
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Wells Oliver | 2017-08-20 23:35:18 | Re: A question on GIN indexes and arrays |
Previous Message | Jerry Sievers | 2017-08-20 23:11:33 | Re: Selecting some schema not suported for libpq PQconnectdbParams |