A high-performance L7 proxy for MySQL and PostgreSQL protocols . 100% open source. Contact us for 24/7 Support, DBRE, Consulting & more!
Joined October 2013
- Tweets 351
- Following 504
- Followers 1,287
- Likes 380
48 Photos and videos
Interesting MySQL 9.7 Community update: JSON Duality Views now support full DML.
Applications can work with JSON documents while MySQL keeps the underlying data relational.
Less JSON plumbing, while preserving relational integrity.
Worth testing with real workloads.
blogs.oracle.com/mysql/no-mo…
#MySQL #JSON
104
Percona Live 2026 showed how broad the open source database ecosystem has become.
MySQL remains strong.
PostgreSQL momentum is impossible to ignore.
Operational challenges are increasingly shared across both.
Our reflections:
proxysql.com/blog/percona-li…
#ProxySQL #PerconaLive #MySQL #PostgreSQL
1
1
89
Thank you to everyone who connected with ProxySQL at Percona Live 2026.
We collected useful follow-up resources for people interested in:
• MySQL scalability
• PostgreSQL traffic management
• HA
• connection pooling
• query routing
• observability
Resources:
proxysql.com/blog/thank-you-…
#PerconaLive #ProxySQL
1
1
97
ProxySQL 3.0.9 and 3.1.9 are out.
3.0.9 is the Stable Tier release recommended for production deployments.
3.1.9 is the Innovative Tier release with FFTO TSDB.
Highlights:
• critical security fixes
• backend-pool session scheduler
• ParserSQL
• PostgreSQL improvements
• MySQL/MariaDB fixes
• packaging hardening
Read more:
proxysql.com/blog/announcing…
98
The hands-on continuation of our Percona Live PostgreSQL talk is now available.
Use dbdeployer to create PostgreSQL replication sandboxes with ProxySQL included.
GET → UNPACK → DEPLOY
Primary, replicas, ProxySQL, helper scripts, pgbench, and ProxySQL stats.
proxysql.com/blog/dbdeployer…
#PostgreSQL #ProxySQL #dbdeployer
64
At Percona Live Bay Area 2026, we presented “ProxySQL – A Perfect Complement to Your PostgreSQL Database.”
The article and presentation are now available.
ProxySQL brings a SQL-aware data gateway model to PostgreSQL: routing, query policy, observability, failover reaction, and runtime configuration.
proxysql.com/blog/a-perfect-…
#PostgreSQL #ProxySQL #PerconaLive
1
1
79
PostgreSQL 19 Beta 1 has been released.
Beta releases are a key testing window not only for database users, but also for the surrounding ecosystem: proxies, drivers, poolers, monitoring, migration, and automation tools.
The temporary protocol grease mode is especially interesting for compatibility testing.
Congratulations to the PostgreSQL community.
postgresql.org/about/news/po…
#PostgreSQL
1
2
105
Great conversations today at Percona Live around MySQL, PostgreSQL, database reliability, and production architecture.
Thank you to everyone who stopped by the ProxySQL booth.
#PerconaLive
46
ProxySQL started in the MySQL ecosystem, solving real production problems around routing, failover, traffic control, and observability.
Now we are bringing the same operational philosophy to PostgreSQL.
Come talk to us at Percona Live.
#ProxySQL #PostgreSQL #MySQL
1
1
55
At Percona Live today?
Bring us your hardest database traffic problem.
Connection storms, failover, replication lag, read/write split, overload, query visibility, routing rules — we are happy to discuss.
#PerconaLive #ProxySQL
50
At Percona Live today?
Let’s talk about the hard parts of running databases in production:
- failover
- replication lag
- connection storms
- read/write split
- observability
- query routing
- overload protection
#ProxySQL #PerconaLive #MySQL #PostgreSQL
1
1
75
Great first day at Percona Live.
Thank you to everyone who connected with ProxySQL yesterday to talk about MySQL, PostgreSQL, database reliability, and production architecture.
Looking forward to more conversations today.
#ProxySQL #PerconaLive
1
45
A database proxy is not “just another hop.”
In production, it can become the control layer for routing, failover, query rules, connection management, traffic shaping, and observability.
That is the role ProxySQL was built for.
#ProxySQL #DatabaseReliability #MySQL
40
Part 4 of our PgBouncer → ProxySQL series is live.
This time we benchmark PostgreSQL extended query protocol and prepared statements.
Encouraging result: ProxySQL performs very well even with 1 worker thread, while offering query rules, routing, visibility, backend awareness, runtime config, and more.
If your PostgreSQL environment needs more than pooling, ProxySQL is worth trying.
proxysql.com/blog/part-4-pgb…
#PostgreSQL
1
3
98
We are proud to join MariaDB Foundation as a Silver Sponsor.
ProxySQL has always been part of the broader MySQL-compatible ecosystem, and MariaDB users have long been part of the ProxySQL community.
For us, this sponsorship is not only about financial support. It is about participation: better communication, stronger collaboration, and continued investment in the open source database infrastructure that many organizations rely on every day.
ProxySQL is committed to supporting MariaDB users with production-grade traffic management, connection handling, read/write splitting, query routing, query rewriting, high availability, observability, and protection from problematic queries.
We are also excited to continue contributing to the surrounding ecosystem through projects such as dbdeployer and orchestrator.
Thank you to MariaDB Foundation for the warm welcome. We look forward to working more closely with the MariaDB community.
mariadb.org/new-sponsor-prox…
1
3
142
We are proud to join MariaDB Foundation as a Silver Sponsor!!
1
2
140
ProxySQL is proud to be a Silver Sponsor of Percona Live 2026 in Mountain View.
We look forward to meeting engineers, DBAs, SREs, architects, and open source database users running real production systems.
#PerconaLive #ProxySQL #MySQL #PostgreSQL
2
68
Read/write split is a policy
Read/write split is not a checkbox.
The hard part is not matching `SELECT`. The hard part is deciding which reads are safe to route away from the writer.
Some reads belong on the primary:
- locking reads
- reads inside write transactions
- read-after-write paths
- session-state-dependent queries
- workloads that cannot tolerate replica lag
Other reads may be safe for replicas:
- reporting queries
- lookup queries
- analytics designed for eventual consistency
- application paths with explicit consistency guarantees
The safest production model is conservative:
1. Default unknown traffic to the writer.
2. Identify known-safe reads.
3. Route those reads to reader hostgroups.
4. Handle exceptions explicitly.
5. Measure the effect.
ProxySQL supports this model with hostgroups and query rules. The routing policy can live in the traffic layer instead of being implemented differently by every application.
The question is not "can reads be split?"
The question is "which reads are safe to split, and under what conditions?"
55
ProxySQL is in the Bay Area this week for the MySQL Contributor Summit and Percona Live 2026.
If you are in Mountain View and want to talk about MySQL, PostgreSQL, query routing, failover, observability, or database reliability, let’s connect.
#ProxySQL #MySQL #PostgreSQL
2
84