The branch switch broke everything.

You were moving fast. git checkout to a feature branch. Migrations done. Code ready. But the app froze the moment it touched the database. The Postgres client code started screaming. It wasn’t the SQL. It wasn’t the schema. It was your connection itself. Binary protocol errors. Stale prepared statements. Caching ghosts stuck in the Postgres binary protocol handshake because the connection never learned the new schema state.

This problem hides in plain sight. You think Postgres is simple until you watch it under a binary protocol proxy when branches keep flipping. Any proxy touching the Postgres wire protocol—PgBouncer, RDS Proxy, custom shims—has to balance speed and correctness. The moment a backend changes its schema but a pooled connection reuses a prepared statement from an old checkout, you crash.

Git checkout proxy pain happens because the Postgres binary protocol is stateful. Clients assume the server remembers what they prepared earlier. Proxies reuse connections to save time. But if the schema changes between uses, the prepared statement IDs that made sense a second ago are gone or now point to something else entirely.

Avoiding this isn’t guesswork. You need a proxy that speaks binary protocol fluently and can reset not just transactions but state. That means clearing prepared statements, resetting session parameters, and forcing a clean handshake whenever you cross a branch boundary. This requires understanding every message type in the Postgres wire protocol: Parse, Bind, Execute, Close, Sync. Get it wrong, and your proxy will leak ghosts into the next session.

Some teams handle this by skipping pooling entirely for branch-based development. Others spin short-lived Postgres instances per branch, but that burns time and resources. The elegant path is a smart proxy that can survive infinite git checkouts without a single protocol mismatch.

Imagine running multiple migrations per hour, flipping branches, hitting your database through a binary protocol proxy, and never worrying about cached statements exploding. That’s not theory. It's working now.

You can see this run for real at hoop.dev. Spin up, connect, and watch Postgres binary protocol proxying stay stable no matter how many times you git checkout. Live in minutes.