News for hackers. Stuff that matters.

A comment on Why we built yet another Postgres connection pooler. Parent comment

Re:Why we built yet another Postgres connection pooler by darkwater on Wednesday July 08, 2026 @04:12AM (#48829052)
> 3. Use a bouncer which can either disallow these changes or detect and revert them after the original client has disconnected. I'm not sure if this exists for MySQL at least.

I believe ProxySQL does exactly that:

* https://proxysql.com/documentation/mysql-prepared-statements...

* https://proxysql.com/documentation/multiplexing/

[ Parent | on HN ]

There are no comments on this comment yet.