Comment 19 for bug 1501781

I can confirm what Blake reports for a fresh install in comment #13.

The problem is that with a fresh install, the extension functions are added to schema public.

When the extension is created in an existing database, the functions are added to the first schema in the search path. In our case, this is schema evergreen.

I recommend changing the upgrade script to create the extension in schema public and then changing the paths.

So, the create extension becomes:

CREATE EXTENSION unaccent SCHEMA public IF NOT EXISTS;

Then the calls to evergreen.unaccent() should be changed to public.unaccent().

Thanks for the effort Dan and for putting up with my suggestions!