Menu

1 / 3

pgcoalesce: a Postgres proxy that merges concurrent point reads

DEV Community: postgres·kobima6813·1 day ago
#A9L53zQv
Reading 0:00
15s threshold

pgcoalesce is a Postgres wire-protocol proxy that holds concurrent primary-key reads of the same shape for a couple of milliseconds, runs them as one query, and fails closed when it cannot prove that is safe. It is not a cache: every answer is read from Postgres at that moment. The only application change is the connection string.

Status: 0.3.0, experimental — benchmarked on one machine, no production users yet. License: Apache-2.0 . Repository: github.com/kobima6813/pgcoalesce .

This write-up covers how the proxy works, the numbers we measured against PgBouncer, the safety model, and how it sits next to other tools in this space. We have not published a benchmark against any product except PgBouncer. Competitor features and prices are from their public docs, checked on 15 November 2026.

The problem

Serverless, edge and API backends often fire many tiny reads at the same moment:

SELECT * FROM users WHERE id = $1

Enter fullscreen mode

Exit fullscreen mode

Each statement is cheap on its own.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.