Presented at Supabase Select 2026 in San Francisco. The full title is Invisible by Design: How Multigres keeps Postgres behaving like Postgres.
A connection pooler does its job when your app can’t tell it’s there. This talk goes inside the Multigres pooler to show what that takes: tracking session settings (including Postgres’s unusual DateStyle), sharing prepared statements across clients and recovering when a schema change makes them stale, scaling LISTEN/NOTIFY through one shared connection, and matching Postgres exactly when you commit a failed transaction.
Related reading: Pooling without choosing a mode · One parse per query, no matter how many gateways · Running a real Postgres app on Multigres, at scale