Re: A question on GIN indexes and arrays

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Wells Oliver <wells(dot)oliver(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 22:15:10
Message-ID: CAMkU=1xnzFYqYpyK8AR=m97WYQ7zTt+KoFEY81hsMY76be4FOA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jerry Sievers 2017-08-20 23:11:33 Re: Selecting some schema not suported for libpq PQconnectdbParams
Previous Message marcelo 2017-08-20 21:54:05 Selecting some schema not suported for libpq PQconnectdbParams