Specify schema in called functions for pg_dump / pg_restore about pgstac

[bitner]

Hmm, I'm not entirely sure what the best course of action for this is. It is not uncommon for people to use the PostgreSQL extension options to install PostGIS to schemas other than public, so I'm not sure it would be good to hard code that to public (at least I know one client of ours where that would definitely break things). I wonder if you set the environment variable PGOPTIONS='-c search_path=public' prior to running the pg_restore if that would work?

[zstatmanweil]

That makes sense. Thanks for the response and brainstorming. I just gave it a shot, and I get the same error as before. I think since pg_dump explicitly sets the search_path to empty right up top with SELECT pg_catalog.set_config('search_path', '', false); that may override the env variable. It does it for some security reason.

I also don't have another idea! This is more a "nice to have". The workaround I have used is creating a database with pypgstac.migrate, exporting item data as ndjson and then bulk loading it back in.