<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Guides on lqo.net</title>
    <link>https://lqo.net/tags/guides/</link>
    <description>Recent content in Guides on lqo.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://lqo.net/tags/guides/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What Is a Learned Query Optimizer? Why PostgreSQL Picks Slow Plans and How to Steer It</title>
      <link>https://lqo.net/what-is-a-learned-query-optimizer-why-postgresql-picks-slow-plans-and-how-to-steer-it/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://lqo.net/what-is-a-learned-query-optimizer-why-postgresql-picks-slow-plans-and-how-to-steer-it/</guid>
      <description>&lt;p&gt;A query optimizer turns your SQL into a plan: which table to read first, which index to use, how to join one table to the next. A learned query optimizer is one that improves its choices from what actually happened when queries ran, instead of trusting its own predictions. The idea is older than it sounds, and it&amp;rsquo;s finally practical.&lt;/p&gt;&#xA;&lt;p&gt;To see why it matters, look at how an ordinary optimizer goes wrong.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
