From: | Julie Nishimura <juliezain(at)hotmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: ERROR: operator class "gin__int_ops" does not exist for access method "gin" |
Date: | 2019-04-18 04:38:43 |
Message-ID: | BYAPR08MB5014E8D6FEAF6A709DD95443AC260@BYAPR08MB5014.namprd08.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thank you! All works now
________________________________
From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Sent: Wednesday, April 17, 2019 5:23 PM
To: Julie Nishimura; pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: ERROR: operator class "gin__int_ops" does not exist for access method "gin"
On 4/17/19 5:18 PM, Julie Nishimura wrote:
> We migrated some tables from 8.3 postgresql to 9.4, and when I compared
> tables DDL between environments, I've noticed some indices are missing
> (majority of them are using GIN
>
> When I am taking 8.3 ddl for it:
> CREATE INDEX serp_test2
> ON serp_test
> USING gin
> (domainids gin__int_ops);
>
> it gives me error:
> ERROR: operator class "gin__int_ops" does not exist for access method "gin"
>
> Is it possible to retrieve the ddl for operator class and recreate it on
> 9.4? If not, is there any work-around?
Looks like it needs the intarray extension:
https://www.postgresql.org/docs/8.3/intarray.html
"There is also a non-default GIN operator class gin__int_ops."
9.4:
https://www.postgresql.org/docs/9.4/intarray.html
>
> Thank you
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | rihad | 2019-04-18 06:52:00 | Multicolumn index for single-column queries? |
Previous Message | Ajay Pratap | 2019-04-18 02:47:47 | Re: PostgreSQL ping/pong to client |