<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>PostgreSQL Labs on Database DevPro</title>
    <link>https://DatabaseDevPro.com/labs/postgresql/</link>
    <description>Recent content in PostgreSQL Labs on Database DevPro</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>jeff.taakey@gmail.com (Jeff Taakey)</managingEditor>
    <webMaster>jeff.taakey@gmail.com (Jeff Taakey)</webMaster>
    <copyright>© 2026 Jeff Taakey</copyright>
    <lastBuildDate>Sat, 07 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://DatabaseDevPro.com/labs/postgresql/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>PostgreSQL Index vs Full Scan: EXPLAIN ANALYZE on 100k / 1M / 5M Rows (Filter &#43; ORDER BY &#43; LIMIT)</title>
      <link>https://DatabaseDevPro.com/labs/postgresql/index-vs-full-scan/</link>
      <pubDate>Sat, 07 Feb 2026 00:00:00 +0000</pubDate>
      <author>jeff.taakey@gmail.com (Jeff Taakey)</author>
      <guid>https://DatabaseDevPro.com/labs/postgresql/index-vs-full-scan/</guid>
      <description>A reproducible lab showing how a composite index changes the execution plan from (parallel) seq scan + sort to index scan + limit, with EXPLAIN (ANALYZE, BUFFERS) evidence on 100k/1M/5M rows.</description>
      
    </item>
    
  </channel>
</rss>
