I was born to sail. The sea teaches lessons that reach far beyond the horizon: respect the sea, trust your crew, adapt to changing conditions, and always keep your course, even when the winds shift.
Today, I’m excited to begin a new voyage as Chief Strategy Officer at @proxysql . Every journey begins with a change of course. Sometimes it means discovering new waters. Sometimes it means sailing familiar seas with a new crew. This is one of those voyages.
I’ve spent more than three decades navigating the world of open source databases, infrastructure, high availability, and the incredible communities that have shaped our industry. The waters are familiar, but the opportunities ahead are anything but.
I’m looking forward to helping chart the next course for ProxySQL, working alongside an exceptional team, and continuing to contribute to the open source ecosystem that has given me so much throughout my career.
Fair winds to my new crew, @rene_cannao and @JesmarCannao
Let’s sail ⛵ ⚓ 🔱
#ProxySQL #Leadership #OpenSource #Databases #MySQL #PostgreSQL #CloudNative #oracleacepro #mysqlrockstar @svrubato
In Daniel's MariaDB test, a primary-key range reading 8 million rows slipped through DBTrail's routing rules. Version 0.128.0 fixed that gap. With @ProxySQL in front, verify where heavy reads actually land:
https://t.co/UWg1vWQUHA
How is vector indexing evolving in MySQL? 🐬
Henrik Ingo explores ongoing InnoDB development, ANN algorithms, ScaNN, and contributions from across the MySQL ecosystem.
Follow the technical discussions and share your ideas!
https://t.co/IM7RNKCTF1
A writer and a reporting replica can serve the same user but need different query budgets. In @ProxySQL 3.0.10+, a hostgroup default lets the timeout follow the destination. MySQL and PostgreSQL examples:
https://t.co/QDwAUKWMub
New from Daniel Guzman: MariaDB HTAP with ProxySQL in front and DBTrail answering heavy reports. The walkthrough covers workload isolation, copy freshness, routing fixes and correctness boundaries.
https://t.co/pg2n5CXWKT
I'm speaking at DuckDB × MySQL Day on Nov 17: embedding DuckDB in @ProxySQL, familiar SQL clients and explicit routing for analytical queries. I'll also preview our native MySQL replication work.
Free and online:
https://t.co/KyVxyv5iO9
Bring your SQL client to DuckDB inside ProxySQL. Part two of our DuckDB series covers query modes, transactions, TLS and what applications receive as results. More articles to follow.
Initial 4.0.12 prerelease, source installation:
https://t.co/HtwcMYaWZy
A MySQL client can now run DuckDB SQL inside @ProxySQL. The embedded tables are separate from backend databases; data is not copied automatically. First article in our DuckDB blog series, with more to follow:
https://t.co/3kGmihkxEL
DuckDB runs inside ProxySQL, with MySQL and PostgreSQL text-query access to one embedded database.
First article in our DuckDB blog series; more to follow. Source installation, 4.0.12 prerelease.
https://t.co/rNgJ0wnG0s
New docs: https://t.co/plwiYPVXrT
Count the tools you open to answer one question: is the database tier healthy right now?
One dashboard for MySQL. Another for PostgreSQL. A session on the ProxySQL admin interface to see what is actually routed where. A wiki page that lists the current config, last edited in March.
None of these are bad tools. The answer just lives in the gaps between them, and the gaps are where incidents hide.
https://t.co/BjkbX5szYH is our attempt to close them: one control plane to manage and monitor MySQL and PostgreSQL environments.
It is in preview ahead of general availability. Early look here: https://t.co/QPvo5VfBQz
#ProxySQL #MySQL #PostgreSQL
The experimental prepared-result cache in ProxySQL 3.1.12/4.0.12 prereleases has protocol limits: MySQL cursor executions and PostgreSQL named portals bypass it. Preparing a read does not make every execution cacheable.
https://t.co/iffB068bMX
During RDS MySQL Blue/Green post-processing, ProxySQL 3.0.10 removes idle backend connections to the old servers. In-use connections are marked non-reusable and destroyed when released. Applications must still handle disconnects.
https://t.co/4nXAxkvxZS
The #MySQL Query Cache was removed because it couldn’t keep up on multicore systems. Was query caching a bad idea? Not necessarily.
@altmannmarcelo (Readyset) explains why — and what works now
📅 Nov 18 · 10:00 AM ET / 16:00 CET · free
https://t.co/m5o8FhfnaW
ProxySQL 3.0.12 embeds OpenSSL 3.5.7 in the executable. Updating the host's OpenSSL package alone does not update that embedded copy. Include the ProxySQL binary in your dependency-upgrade plan.
https://t.co/iffB068bMX
A paused PostgreSQL fetch still owns a backend connection. @ProxySQL 3.1.12/4.0.12 prereleases support named portals through the native TCP backend path, keeping the connection attached while the portal is open.
https://t.co/hxhUhaKYhv