<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Postgresql on lqo.net</title>
    <link>https://lqo.net/tags/postgresql/</link>
    <description>Recent content in Postgresql on lqo.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://lqo.net/tags/postgresql/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>First LQO Release Finds the PostgreSQL Queries a Planner Setting Makes Faster</title>
      <link>https://lqo.net/first-lqo-release-finds-the-postgresql-queries-a-planner-setting-makes-faster/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://lqo.net/first-lqo-release-finds-the-postgresql-queries-a-planner-setting-makes-faster/</guid>
      <description>&lt;p&gt;Every PostgreSQL database has a few queries the planner gets badly wrong. Not slow because they&amp;rsquo;re big. Slow because the planner guessed the wrong row count, picked a plan for ten rows, and got ten thousand. Finding them is usually an afternoon with &lt;code&gt;EXPLAIN ANALYZE&lt;/code&gt;, one query at a time.&lt;/p&gt;&#xA;&lt;p&gt;LQO 0.1 does that afternoon for a whole workload. Give it a server log or a file of queries, point it at a replica, and it runs each kind of query under PostgreSQL&amp;rsquo;s default plan and under a set of planner settings. Then it tells you which settings make which queries clearly faster, with the exact lines to use.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
