Re: [GENERAL] A question on GIN indexes and arrays - Mailing list pgsql-general

From Jeff Janes
Subject Re: [GENERAL] A question on GIN indexes and arrays
Date
Msg-id CAMkU=1xnzFYqYpyK8AR=m97WYQ7zTt+KoFEY81hsMY76be4FOA@mail.gmail.com
Whole thread Raw
In response to [GENERAL] A question on GIN indexes and arrays  (Wells Oliver <wells.oliver@gmail.com>)
Responses Re: [GENERAL] A question on GIN indexes and arrays  (Wells Oliver <wells.oliver@gmail.com>)
List pgsql-general
On Sun, Aug 20, 2017 at 1:28 PM, Wells Oliver <wells.oliver@gmail.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

pgsql-general by date:

Previous
From: marcelo
Date:
Subject: [GENERAL] Selecting some schema not suported for libpq PQconnectdbParams
Next
From: Jerry Sievers
Date:
Subject: Re: [GENERAL] Selecting some schema not suported for libpq PQconnectdbParams