You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
schema "pg_pgrst_no_exposed_schemas" does not exist
Why this happens
This error is seen when the Data API is disabled on the Supabase project.
Currently, we don't really shutdown PostgREST when the Data API is disabled. You will see a schema called pg_pgrst_no_exposed_schemas added in the exposed schemas.
This should not adversely affect the project, although it may result in additional entries in your logs.
We're aware of this issue and are working on it.
Workaround
To stop the missing-schema log entries:
Open the SQL Editor.
Run the following statements:
-- Create a schema with nothing insidecreateschemapgrst_no_exposed_schemas;
-- Set the db-schemas configuration
alter role authenticator setpgrst.db_schemas='pgrst_no_exposed_schemas';
-- Reload PostgREST's schema cache and configuration
notify pgrst;
PostgREST now exposes an empty schema, which stops the missing-schema errors.
Re-enabling the Data API in the future
You may decide that you wish to re-enable the Data API in the future.
If you do so, to reverse the workaround, you can run the following statements before re-enabling the Data API:
Open the SQL Editor.
Run the following statements:
-- Reset the db-schemas configuration
alter role authenticator reset pgrst.db_schemas;
-- Reload PostgREST's schema cache and configuration
notify pgrst;
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
PostgREST logs showing the error:
schema "pg_pgrst_no_exposed_schemas" does not existWhy this happens
pg_pgrst_no_exposed_schemasadded in the exposed schemas.Workaround
To stop the missing-schema log entries:
Open the SQL Editor.
Run the following statements:
PostgREST now exposes an empty schema, which stops the missing-schema errors.
Re-enabling the Data API in the future
You may decide that you wish to re-enable the Data API in the future.
If you do so, to reverse the workaround, you can run the following statements before re-enabling the Data API:
Open the SQL Editor.
Run the following statements:
Related topics
All reactions