skip to content
B³ Logo

Tags → #postgres

2026

  • One parse per query, no matter how many gateways

    In a single database, prepared statements parse once. Behind many gateways that win quietly evaporates. How Multigres consolidates prepared statements so Postgres parses each one exactly once.

  • Pooling without choosing a mode

    Connection pool modes force a tradeoff between performance and correctness. Multigres figures out per-query which mode a connection needs, so you never have to choose statement, transaction, or session mode.

  • Per-user pools that share fairly

    Why Multigres gives every user a dedicated connection pool (mostly a security story), how it shares a fixed budget fairly with max-min fairness, and the bucketing trick that keeps lookup fast.

  • Two jobs, two processes: why Multigres has its own pooler

    Most connection poolers do two jobs in one process. Multigres splits them: multigateway accepts clients, multipooler manages backends. This is why.

  • A 2.5x faster Postgres parser with Claude Code

    Same engineer. Same complexity. A year last time, eight weeks this time. This isn't a story about AI writing code. It's a story about the system, expertise, and discipline that made AI actually useful.