<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Maintenance on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/maintenance/</link>
    <description>Recent content in Maintenance on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 11 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/maintenance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted PostgreSQL Table Maintenance: pg_repack vs pg_squeeze vs pgcompacttable 2026</title>
      <link>https://www.pistack.xyz/posts/2026-05-11-postgresql-table-maintenance-pg-repack-pg-squeeze-pgcompacttable/</link>
      <pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-11-postgresql-table-maintenance-pg-repack-pg-squeeze-pgcompacttable/</guid>
      <description>&lt;p&gt;PostgreSQL&amp;rsquo;s MVCC (Multi-Version Concurrency Control) architecture means that every UPDATE and DELETE leaves behind dead tuples. Over time, these dead tuples accumulate as table bloat, degrading query performance and wasting disk space. While PostgreSQL&amp;rsquo;s autovacuum daemon handles basic cleanup, it cannot rebuild tables or indexes without acquiring exclusive locks that block all reads and writes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
