schema "pg_pgrst_no_exposed_schemas" does not exist
Last edited: 8/4/2026
PostgREST logs showing the error:
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_schemasadded 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:
1-- Create a schema with nothing inside2create schema pgrst_no_exposed_schemas;34-- Set the db-schemas configuration5alter role authenticator set pgrst.db_schemas = 'pgrst_no_exposed_schemas';67-- Reload PostgREST's schema cache and configuration8notify pgrst;
PostgREST now exposes an empty schema, which stops the missing-schema errors.
Re-enable the Data API#
Before you re-enable the data API:
-
Open the SQL Editor.
-
Run the following statements:
1-- Reset the db-schemas configuration2alter role authenticator reset pgrst.db_schemas;34-- Reload PostgREST's schema cache and configuration5notify pgrst;