Error: schema "vaults" does not exist
Need help!
An internal PostgREST schema introspection query is failing due to a naming discrepancy. The system is attempting to query a non-existent "vaults" (plural) schema, while the project only contains a "vault" (singular) schema.
Error Symptoms:
Database initialization fails
Unable to perform schema introspection
Potential blockage of application startup
I'm getting this error:
There was nothing fiddled with the schemas. The project was running up until a month ago. Cant seem to understand why is this happening. Updated Postgres from 15 to 17, thought maybe it would reinit somehow, but still having same issue.
Any help is appreciated!
4 Replies
PostgREST does not use vault, but maybe you meant Postgres.
There should be nothing in Postgres or Supabase side code references a schema called vaults.
Oh yes, sorry, I meant Postgres. But then again it somehow references
vaults schema 🤷♂️ there is a vault schema. The thing is that everything was working and no changes deployed. It just happened. I'm trying to figure out if there is a way to fix this...If anyone in the future gets a similar error – I found that somehow in the Settings, under Data API
vaults has been added as an exposed schema.
You should check if anyone else has access to your account as that schema is never exposed. That would be a security issue if it was ever exposed. To me it's either someone else has access to your account and was trying to expose that schema or you added it there accidentally and forgot.