<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Performance on Tech Notes - A Developer's Journal</title><link>https://oypron.com/tags/performance/</link><description>Recent content in Performance on Tech Notes - A Developer's Journal</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 12 Jan 2026 16:30:00 +0000</lastBuildDate><atom:link href="https://oypron.com/tags/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Postgres Performance Tuning: The First Five Things I Check</title><link>https://oypron.com/posts/postgres-performance-tuning/</link><pubDate>Mon, 12 Jan 2026 16:30:00 +0000</pubDate><guid>https://oypron.com/posts/postgres-performance-tuning/</guid><description>&lt;p&gt;When somebody hands me a Postgres database and says &amp;ldquo;it&amp;rsquo;s slow,&amp;rdquo; I work through the same checklist almost every time. None of these are exotic. They&amp;rsquo;re the boring, high-leverage things that solve maybe 80 percent of the cases I see before anyone has to think hard.&lt;/p&gt;
&lt;h2 id="1-explain-analyze-buffers-before-anything-else"&gt;1. EXPLAIN (ANALYZE, BUFFERS) before anything else&lt;/h2&gt;
&lt;p&gt;Theories about why a query is slow are mostly worthless. Run the query with &lt;code&gt;EXPLAIN (ANALYZE, BUFFERS)&lt;/code&gt; and read the output.&lt;/p&gt;</description></item></channel></rss>