Supabase Agent for Gluesync: Target Integration

Target Supabase

Agent changelog

PostgreSQL target advanced settings

Supabase is PostgreSQL, and it speaks the PostgreSQL wire protocol. This agent is therefore the PostgreSQL target with Supabase’s connection defaults: it connects through the built-in PostgreSQL JDBC driver to database postgres as user postgres, with TLS on, and it uses the same type mapping, snapshot and CDC write paths and bulk COPY path as the PostgreSQL target.

Gluesync does not call the Supabase REST API or the Supabase management API. It needs only a database connection, so it works with Supabase projects hosted on supabase.com and with self-hosted Supabase.

The full-catalog walk of Core Hub (see PII discovery and masking) treats the schemas Supabase manages for itself (auth, storage, realtime, vault, extensions, graphql and the like) as system schemas: it does not walk or sample them, so auth.users and its password hashes are never read. Your own tables, in public or in schemas you created, are walked as usual.

Supabase Postgres 15 or later, hosted or self-hosted, over the direct connection or the session pooler.

The integration test suite runs against Supabase Postgres 17.6 (the supabase/postgres image, version 17.6.1.054), with the postgres role (not a superuser, as on hosted Supabase), TLS only, row level security, the supabase_realtime publication and extensions installed in the extensions schema. This is not a certified compatibility matrix.