Testing the Connection Pooling in Multigres: What does 100% pass rate mean?
How we test connection pooling in Multigres, and what a 100% pass rate actually tells you about correctness.
Multigres Blog
How Multigres Supports LISTEN/NOTIFY Across Pooled Connections
LISTEN/NOTIFY is a per-session feature, and Multigres pools connections away from clients. Here's how we keep Postgres's pub/sub working when no client owns a backend session.
Building a Truly Compatible Postgres Proxy: The Multigres Story
True Postgres compatibility means a client can't tell it's talking to a proxy — not at the wire, not in a message, not in a diagnostic field. What we learned chasing that bar while building Multigres, and how we measure it with Postgres's own regression suite instead of asserting it.
- Deploying the Multigres Operator
- Handling edge cases using consensus
- Postgres High Availability from first principles
- Running a real Postgres app on Multigres, at scale
- How a Multigres Cluster Bootstraps
- One parse per query, no matter how many gateways
- Per-user pools that share fairly
- Pooling without choosing a mode
- Two jobs, two processes: why Multigres has its own connection pooler
- How TLA+ Caught a Silent Data Divergence Bug in Postgres’s pg_rewind
- A 2.5x faster Postgres parser with Claude Code
- Generalized Consensus: Recap
- Generalized Consensus: Addenda
- Generalized Consensus: Consistent Reads
- Generalized Consensus: Changing the Rules
- Generalized Consensus: Discovery and Propagation
- Generalized Consensus: Revocation and Candidacy
- Generalized Consensus: Ordering Decisions
- Generalized Consensus: Fulfilling Requests
- Generalized Consensus: Governing Rules
- Generalized Consensus: Setting the Requirements
- Generalized Consensus: Defining the Problem
- Introducing Generalized Consensus: An Alternate Approach to Distributed Durability
- High Availability and Postgres full-sync replication
- Interview: Multigres on Postgres.FM
- Interview: Multigres on Database School
