Skip to content

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_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:

  1. Open the SQL Editor.

  2. Run the following statements:

    1
    -- Create a schema with nothing inside
    2
    create schema pgrst_no_exposed_schemas;
    3
    4
    -- Set the db-schemas configuration
    5
    alter role authenticator set pgrst.db_schemas = 'pgrst_no_exposed_schemas';
    6
    7
    -- Reload PostgREST's schema cache and configuration
    8
    notify 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:

  1. Open the SQL Editor.

  2. Run the following statements:

    1
    -- Reset the db-schemas configuration
    2
    alter role authenticator reset pgrst.db_schemas;
    3
    4
    -- Reload PostgREST's schema cache and configuration
    5
    notify pgrst;