A Postgres pooler that fixes the leak where one client's session bleeds into another (pgdog.dev)
PgDog ships its own SQL parser so it can track SET, LISTEN/NOTIFY and prepared statements per client and restore them before each query, the exact features PgBouncer's transaction mode makes you give up. Kokotov says it's run a year in production at 2M queries/sec.
The thread's war stories agreed the tax is real: one engineer who'd just moved a Django app behind PgBouncer found queryset.iterator()'s server-side cursors didn't survive pooling, and statement_timeout in libpq startup params got silently ignored.
Sign in to save