Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

chandana-postgrest-multiple-schema-objects (#44651)

Chandana Anumulab694fbdc753b
diff --git a/apps/docs/content/troubleshooting/postgrest-not-recognizing-objects-in-schema b/apps/docs/content/troubleshooting/postgrest-not-recognizing-objects-in-schema
new file mode 100644
index 00000000000..fa5a15efd65
--- /dev/null
+++ b/apps/docs/content/troubleshooting/postgrest-not-recognizing-objects-in-schema
@@ -0,0 +1,25 @@
+---
+title = "PostgREST not recognizing the objects(tables/functions/views) in a schema even after adding it to the exposed schemas"
+topics = [
+ "database",
+ "rest-api",
+ "platform"
+]
+keywords = []
+---
+
+PostgREST is returning errors by not recognizing the objects(tables/functions/views) in a schema and logging errors similar to:
+
+```
+Could not find the table 'X' in the schema cache
+```
+
+## Why this happens
+
+When multiple schemas are exposed, the first entry in the list is treated as the default, so PostgREST resolves unqualified object names only against that schema.
+
+This behavior is intentional, as it prevents conflicts when different schemas contain objects with the same name.
+
+## How to fix this
+
+If you want to use the objects without specifying a schema, you'd need to put it first. Else, you should initialise the Supabase client with the schema([”With custom schemas”](https://supabase.com/docs/reference/javascript/initializing)) or specify the schema on each request using ".schema('your_schema')" (["Switching schemas per query"](https://supabase.com/docs/reference/javascript/select))
diff --git a/apps/docs/content/troubleshooting/schema-pg_pgrst_no_exposed_schemas-does-not-exist b/apps/docs/content/troubleshooting/schema-pg_pgrst_no_exposed_schemas-does-not-exist
new file mode 100644
index 00000000000..853f108969b
--- /dev/null
+++ b/apps/docs/content/troubleshooting/schema-pg_pgrst_no_exposed_schemas-does-not-exist
@@ -0,0 +1,21 @@
+---
+title = "schema \"pg_pgrst_no_exposed_schemas\" does not exist"
+topics = [
+ "database",
+ "rest-api",
+ "platform"
+]
+[[errors]]
+message = "schema pg_pgrst_no_exposed_schemas does not exist"
+---
+
+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 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.