Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #5080

P

ProxySQL

Company blog · proxysql.com/blogdatasystems

ProxySQL is the company blog at proxysql.com, writing about data and systems. Since 2016, 15 different Hacker News readers have linked it 18 times, most often “100K+ Connections with MySQL”. It is still writing: the last post was on 2026-10-27, and you can follow it by feed.

Visit the blog
18mentions?
15HN people?
2016–2026first – last linked?
Links on Hacker News per year · peak 3 in 2017

Too few sampled comments (8) to say how often HN recommends it.?

Why HN links it

HN commenters mention the ProxySQL site as the home of a MySQL and Postgres proxy used for connection pooling, multiplexing and failover. The comments discuss the tool, not the site's writing.

Summarised by Claude from a sample of 8 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

The intelligent database proxy trusted to route, balance, and protect mission-critical MySQL and PostgreSQL workloads at scale.

Most-linked posts?

  1. 100K+ Connections with MySQL
    5 people · 5 mentions · first linked 2018-10-15
  2. ProxySQL
    2 people · 2 mentions · first linked 2016-12-30

What Hacker News says?

  1. > replication options like multi-source MySQL 5.7 supports multi-source replication: https://dev.mysql.com/doc/refman/5.7/en/replication-channels... > spider for sharding and galera are all built in and actively maintained. Galera is available in MySQL-compatible binaries from Percona (Percona-XtraDB-Cluster): https://www.percona.com/software/mysql-database/percona-xtra... MySQL also has their own Paxos-compliant cl…

    Comment linking /

    on “Migrating Facebook to MySQL 8.0”
  2. Submitted Scaling MySQL with ProxySQL as a story · 19 points

    HN discussion
  3. I don't think the claim of MySQL replication being better is related to statement vs. row vs. binary diff. I think it is about the tooling and community knowledge about replication, and about running MySQL in large scale production environments in general. MySQL is run more often at extremely large scale (Facebook, YouTube, Twitter, Dropbox, etc.) than Postgres. That results in very battle tested and/or featureful t…

    Comment linking /

    on “PostgreSQL HA cluster failure: a post-mortem”
  4. Submitted ProxySQL integrates ClickHouse with MySQL protocol as a story · 10 points

    HN discussion
  5. note that while the MySQL connection-pool equation is pretty different from that of Postgresql's, at least in my experience MySQL connections use less memory (sorry, no measurements handy, feel free to correct me, but they generally are handled as a thread rather than an entire subprocess and we regularly see apps that spin up thousands of them fairly cheaply) and also have a lower startup time (also anecdotal, sorr…

    Comment linking /

    on “How to Manage Connections Efficiently in Postgres, or Any Database”
  6. Submitted ProxySQL as a story · 4 points

    HN discussion
  7. We use proxysql ( https://proxysql.com ) which works very well. We have not seen any downtime for years. We wrote our own master promotion code a very long time ago; it has proven to be very robust.

    Comment linking /

    on “PostgreSQL High Availability Solutions – Part 1: Jepsen Test and Patroni”
  8. Submitted ProxySQL Now Supports PostgreSQL as a story · 2 points

    HN discussion
  9. Unfortunately, it won't. Traditional MySQL replication does not provide a built-in option for fully synchronous behavior. You can optionally use MySQL's "semi-sync" replication feature, in which replicas ACK receipt of transactions. This is purely for durability though, not consistency: it ensures commits are durable even if the primary DB has an unrecoverable hardware failure, but without having the massive latency…

    Comment linking /blog/proxysql-gtid-causal-reads/

    on “My thoughts about Fly.io (so far) and other newish technology I'm getting into”
  10. Submitted ProxySQL vs. MaxScale: Persistent Connection, response time, and bugs as a story · 2 points

    HN discussion
  11. 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

    Comment linking /

    on “Postgres Postmaster does not scale”
  12. Submitted The future of Orchestrator: ProxySQL takes takes the helm as a story · 1 points

    HN discussion
  13. There has been ClickHouse MySQL Access through ProxySQL for years. It is great it is now available out of the box! https://www.proxysql.com/blog/clickhouse-and-proxysql-querie...

    Comment linking /blog/clickhouse-and-proxysql-queries-rewrite

    on “ClickHouse and MySQL – Better Together”
  14. Submitted ProxySQL as a story · 1 points

    HN discussion
  15. > 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/

    Comment linking /documentation/multiplexing/

    on “Why we built yet another Postgres connection pooler”
  16. Submitted 100K+ Connections with MySQL as a story · 1 points

    HN discussion
  17. Submitted Scaling with ProxySQL Query Cache as a story · 1 points

    HN discussion

Search all of HN for proxysql.com

Linked by the same people?