@supabase/pg-delta 1.0.0-alpha.19 → 1.0.0-alpha.20

package/dist/core/integrations/supabase.js

@@ -143,14 +143,29 @@ export const supabase = {
                 skipAuthorization: true,
             },
         },
-        // pgmq extensions creates it's own schema on install doing a `CREATE EXTENSION pgmq WITH SCHEMA pgmq;`
-        // will cause an error because the schema will create extension and extension refer to unexisting schema
+        // Extensions whose install script creates its own target schema cannot
+        // tolerate `CREATE EXTENSION … WITH SCHEMA <self>` against a fresh
+        // database: Postgres resolves WITH SCHEMA before running the extension's
+        // script, so the schema referenced by the clause does not exist yet.
+        // These extensions also install into schemas listed in
+        // SUPABASE_SYSTEM_SCHEMAS, so pg-delta filters their CREATE SCHEMA out
+        // of the declarative plan — nothing else will pre-create the schema.
+        // Emitting a bare `CREATE EXTENSION <name>` lets the extension's own
+        // install script create the schema it expects.
+        //
+        // Note: other extensions install into SUPABASE_SYSTEM_SCHEMAS too
+        // (`pg_graphql` → `graphql`, `supabase_vault` → `vault`,
+        // `uuid-ossp`/`pgcrypto`/`pg_net`/`pg_stat_statements` → `extensions`),
+        // but those schemas are created by the supabase/postgres image baseline
+        // and survive `DROP EXTENSION … CASCADE`, so `CREATE EXTENSION … WITH
+        // SCHEMA <schema>` finds the schema and succeeds. Only the three below
+        // have self-created schemas that are absent from the baseline.
         {
             when: {
                 objectType: "extension",
                 operation: "create",
                 scope: "object",
-                "extension/schema": ["pgmq"],
+                "extension/schema": ["pgmq", "pgsodium", "pgtle"],
             },
             options: {
                 skipSchema: true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@supabase/pg-delta",
-  "version": "1.0.0-alpha.19",
+  "version": "1.0.0-alpha.20",
   "description": "PostgreSQL migrations made easy",
   "type": "module",
   "sideEffects": false,

package/src/core/integrations/supabase.ts

@@ -148,14 +148,29 @@ export const supabase: IntegrationDSL = {
         skipAuthorization: true,
       },
     },
-    // pgmq extensions creates it's own schema on install doing a `CREATE EXTENSION pgmq WITH SCHEMA pgmq;`
-    // will cause an error because the schema will create extension and extension refer to unexisting schema
+    // Extensions whose install script creates its own target schema cannot
+    // tolerate `CREATE EXTENSION … WITH SCHEMA <self>` against a fresh
+    // database: Postgres resolves WITH SCHEMA before running the extension's
+    // script, so the schema referenced by the clause does not exist yet.
+    // These extensions also install into schemas listed in
+    // SUPABASE_SYSTEM_SCHEMAS, so pg-delta filters their CREATE SCHEMA out
+    // of the declarative plan — nothing else will pre-create the schema.
+    // Emitting a bare `CREATE EXTENSION <name>` lets the extension's own
+    // install script create the schema it expects.
+    //
+    // Note: other extensions install into SUPABASE_SYSTEM_SCHEMAS too
+    // (`pg_graphql` → `graphql`, `supabase_vault` → `vault`,
+    // `uuid-ossp`/`pgcrypto`/`pg_net`/`pg_stat_statements` → `extensions`),
+    // but those schemas are created by the supabase/postgres image baseline
+    // and survive `DROP EXTENSION … CASCADE`, so `CREATE EXTENSION … WITH
+    // SCHEMA <schema>` finds the schema and succeeds. Only the three below
+    // have self-created schemas that are absent from the baseline.
     {
       when: {
         objectType: "extension",
         operation: "create",
         scope: "object",
-        "extension/schema": ["pgmq"],
+        "extension/schema": ["pgmq", "pgsodium", "pgtle"],
       },
       options: {
         skipSchema: true,