<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>ProxySQL Blog — #prepared-statements</title><description>Posts tagged #prepared-statements on the ProxySQL blog.</description><link>https://proxysql.com/</link><language>en-us</language><item><title>Part 4 - PgBouncer to ProxySQL: Extended and Prepared Protocols</title><link>https://proxysql.com/blog/part-4-pgbouncer-to-proxysql/</link><guid isPermaLink="true">https://proxysql.com/blog/part-4-pgbouncer-to-proxysql/</guid><description>Part 4 of the PgBouncer to ProxySQL series. Benchmarks ProxySQL and PgBouncer under PostgreSQL&apos;s extended and prepared query protocols. ProxySQL keeps the lead and widens it as worker threads increase.</description><pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate><author>Rahim Kanji</author></item><item><title>ProxySQL&apos;s prepared statement cache refactor, explained</title><link>https://proxysql.com/blog/proxysql-3-0-4-prepared-statement-cache-refactor/</link><guid isPermaLink="true">https://proxysql.com/blog/proxysql-3-0-4-prepared-statement-cache-refactor/</guid><description>A walk-through of the PostgreSQL prepared-statement cache refactor — what was slow, why, and how the redesign turned a contended path into a contention-free one</description><pubDate>Fri, 17 Apr 2026 00:00:00 GMT</pubDate><author>Rahim Kanji</author></item></channel></rss>