Type matching issues when using different schemas about postgrex HOT 5 CLOSED

Reverting to type will cause other issues: #233

You have to make sure citext is installed on all schemas instead. Check out the issues tracker for previous issues. :)

from postgrex.

Thank you for such a quick response :)

You have to make sure citext is installed on all schemas instead. Check out the issues tracker for previous issues. :)

I'm not sure what you mean by that. There doesn't seem to be a way to install extensions on multiple schemas (for example ALTER EXTENSION citext SET SCHEMA public, foo; gives a syntax error). Are you suggesting the extension should be moved to pg_catalog?

I read some other issues, but none of the suggestions seemed to work / apply in my case. Sorry if this is a duplicate.

from postgrex.

I believe you have to create the extension again, but now in another schema. You can also have a schema with all extensions and then keep it in the search path too.

from postgrex.

Creating the extension again in a different schema fails [42710] ERROR: extension "citext" already exists. It seems extensions are global. I can't just move this extension to the foo schema, because it would cause the same issue for the user that works with the public schema.

The solution with all extensions in a different schema (added to search_path) seems to work.

For future reference, this seems to work:

CREATE SCHEMA extensions;
ALTER EXTENSION citext SET SCHEMA extensions;
ALTER USER foo SET search_path = foo, extensions;

Thank you. Should I close this issue?

from postgrex.

Thank you for following up with detailed steps for future reporters. It seems we are good now, thank you!

from postgrex.