Framework
Reports that share this framework, grouped in one feed.
The pg-meta schemas update and remove methods construct DO blocks with fixed $$ dollar-quote delimiters. If any interpolated identifier (schema name, new name, or owner) contains the byte sequence '$$', the PostgreSQL parser prematurely closes the dollar quote, leading to a syntax error and potential SQL injection if the truncation leaves executable statements.
A disk-full event during a migration caused PostgreSQL to crash with SQLSTATE 53100. After expanding disk to 8GB, crash recovery checkpoint completed and read-only mode ended, but all connection methods (Supavisor, direct, REST, SQL Editor) remain timed out, indicating the PostgreSQL backend is not accepting connections or is stuck in a state that prevents normal operation.
pgMeta.tables.update (primary_keys path) and pgMeta.columns.update (is_unique:false and check paths) build DO $$ ... $$ blocks that embed identifiers via ident(), causing syntax error when any identifier contains the literal byte sequence $$.
The Supabase realtime prompt documentation contains an invalid PostgreSQL row-level security policy example that uses USING with FOR INSERT. This prevents users from creating the documented private-channel write policy.