<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Performance-Tuning on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/performance-tuning/</link>
    <description>Recent content in Performance-Tuning on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 15 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/performance-tuning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Database Query Rewrite — pg_hint_plan vs MySQL Query Rewrite vs MaxScale Query Rewrite</title>
      <link>https://www.pistack.xyz/posts/2026-05-15-self-hosted-database-query-rewrite-pg-hint-plan-mysql-maxscale-guide/</link>
      <pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-15-self-hosted-database-query-rewrite-pg-hint-plan-mysql-maxscale-guide/</guid>
      <description>&lt;p&gt;Database query performance is one of the most common bottlenecks in production systems. Sometimes the query optimizer makes sub-optimal choices — selecting a sequential scan when an index scan would be faster, or joining tables in the wrong order. &lt;strong&gt;Query rewrite tools&lt;/strong&gt; let you override or redirect problematic queries without modifying application code.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
