Supabase

Supabase runs Postgres with logical replication already enabled. Connect it like any Postgres source.

Connection

• Use the direct connection string, not the pooler — replication needs a direct, long-lived connection.
• Point at the writable primary (pg_is_in_recovery() must be false); preflight checks this as is writer.
• wal_level is already logical on Supabase.

Schema tracking without superuser

The postgres role on Supabase is not a raw superuser, but Supabase’s supautils grants it privileged-role powers, including creating event triggers. anybranch detects this: preflight reports can create event trigger as a privileged role, so schema-change replay works as the postgres role. Verified against the supabase/postgres image.

Extensions

The schema copy uses pg_dump --schema-only. Extensions the source uses that are not installed on the anybranch server surface as schema-load warnings (saved to run/schema.log); rows still replicate. Install the extensions you depend on on the server, or accept that extension-owned objects are absent on branches.