no schema has been selected to create in (SQLSTATE 3F000) after upgrading from 3.18.0 to 3.19.2

[kevintsou17]

I'm wondering if anyone has faced a similar issue after upgrading from 3.18.0 to 3.19.2. After the upgrade, we encountered the "No schema has been selected to create in (SQLSTATE 3F000)" issue.

[mfridman]

Is it possible you've also updated your Postgres instance to version 15 or higher?

This error typically has to do with the search path, either:

1. it's empty (which is what pg_dump by default, SELECT pg_catalog.set_config('search_path', '', false);)
2. it's invalid
3. insufficient roles for whatever schema you have

The reason I ask about Postgres 15 or higher, is because there was changes specifically related to this. Check out the release notes and search for "public schema".

[mfridman]

That is very peculiar. The major changes between those 2 releases:

v3.18.0...v3.19.2

• a fix to remapping redshift / postgres to a driver
• making goose annotations case-insensitive
• updating all the dependencies

Do you use goose as a library (importing in your project) or as a CLI (either go install or downloading released binaries)?

[kevintsou17]

sorry for the late response.
We use goose as library and run it in the code.

[kevintsou17]

Just following up on this.
Thanks.

[mfridman]

Hey there, I would love to help you, but don't immediately see what the problem could be. I'll audit the changes to see if there's a good explanation for this.

If possible, a reproducible example, or even just the failing migration, or any other kind of details, would help debug this .

[kevintsou17]

I will try to investigate further, and if there's still no resolution, I will post a reproducible example. Thank you.