gin_trgm_ops does not exist for access method "gin"

[beckmx]

Hello, I have been working on a project that is shared by several members, and lately I cannot use my postgress installation for this problem:

PG::UndefinedObject: ERROR: operator class "gin_trgm_ops" does not exist for access method "gin"

Any ideas?

[tbussmann]

seems you don't have the pg_trgm extension installed in the database in question. Try CREATE EXTENSION pg_trgm;

[sailing]

Even with the extension installed, I still see this, on 9.4.9.1

[sailing]

@beckmx, to clarify what @tbussmann responded, you need to \c to the database in question before running CREATE EXTENSION pg_trgm;

By default PostgresApp has you on your personal DB.

[quocgfy]

Works great for me. thanks!

[jakob]

Glad it worked! Since there's nothing to do for us here, I'm closing this issue.

[leandropadua]

Thanks for the solution. That worked partially for me. The full solution was to apply it to every schema by adding the schema pg_catalog to the end of it:
create extension pg_trgm with schema pg_catalog;

[maufranchini]

It worked for me as well, with another extension related to GIN (intarray). I needed to select the schema as @leandropadua mentioned.

create extension intarray with schema nameOfMySchema

[jiapei100]

@beckmx, to clarify what @tbussmann responded, you need to \c to the database in question before running CREATE EXTENSION pg_trgm;

By default PostgresApp has you on your personal DB.

Thank you so much....

[Que2701]

@tbussmann works for me

[rulasmarmol]

In my case I already had the extension installed, but I created a new schema and it was not working with the new schema, so I had to drop the extension and create a new one specifying the schema and that work.

[lauksas]

In my case, some other script created the extension in a non-standard schema, thus the gin_trgm_ops was not being found.
I issued ALTER EXTENSION pg_trgm SET SCHEMA pg_catalog; to my script and it worked.
Hope that helps someone.

[alistairreynolds]

In my case it was a bit different. I was restoring using a dump file of a separate schema (not including the public schema), so when restoring into the target database where I'd already had the extension created, it could only create it on the public schema, not the new one. And I couldn't create the extension on the target schema because it hadn't been created yet (slightly chicken-egg).

Only real way around it was to re-create the extension on the target schema after it had finished reimporting, then re-adding the indexes