<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>The Name on lqo.net</title>
    <link>https://lqo.net/tags/the-name/</link>
    <description>Recent content in The Name 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/the-name/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why LQO Stands for Learned Query Optimizer, and What It Learns</title>
      <link>https://lqo.net/why-lqo-stands-for-learned-query-optimizer-and-what-it-learns/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://lqo.net/why-lqo-stands-for-learned-query-optimizer-and-what-it-learns/</guid>
      <description>&lt;p&gt;LQO is short for learned query optimizer, the name database researchers use for an optimizer that improves from what queries actually did rather than from its own predictions. Say it as three letters, L-Q-O. The name is plain on purpose. It says what the thing is to the people most likely to look for it.&lt;/p&gt;&#xA;&lt;p&gt;Each word does some work, though, and one of them needs an honest footnote.&lt;/p&gt;&#xA;&lt;h2 id=&#34;query-optimizer&#34;&gt;Query Optimizer&lt;/h2&gt;&#xA;&lt;p&gt;Every SQL database has an optimizer. It&amp;rsquo;s the part that decides how to run your query: which table first, which index, which way to join. You don&amp;rsquo;t see it, but it&amp;rsquo;s the reason the same SQL can take 4 ms or 4 seconds. PostgreSQL&amp;rsquo;s optimizer is the planner, and LQO works with it rather than around it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
