zlacker

[return to "Postgres Postmaster does not scale"]
1. vel0ci+o12[view] [source] 2026-02-05 04:26:25
>>davidg+(OP)
Isn't this kind of the reason why teams will tend to put database proxies in front of their postgres instances, to handle massive sudden influxes of potentially short lived connections?

This sounds exactly like the problem tools like pgbouncer were designed to solve. If you're on AWS one could look at RDS Proxy.

◧◩
2. evanel+U22[view] [source] 2026-02-05 04:41:24
>>vel0ci+o12
Also check out ProxySQL [1][2], it's an extremely powerful and battle-tested proxy. Originally it was only for MySQL/MariaDB, where it is very widely used at scale, even despite MySQL already having excellent built-in scalable threaded connection management. But ProxySQL also added Postgres support too in 2024 and that has become a major focus.

[1] https://proxysql.com/

[2] https://github.com/sysown/proxysql

◧◩◪
3. srouss+l32[view] [source] 2026-02-05 04:46:28
>>evanel+U22
And lets you rewrite queries on the fly. :)
[go to top]