<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>insightral Blog</title>
    <link>https://insightral.com/blog</link>
    <description>Practical Postgres guides for engineers: connection pools, missing indexes, slow queries, and more.</description>
    <language>en-us</language>
    <lastBuildDate>Wed, 24 Jun 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://insightral.com/blog/rss.xml" rel="self" type="application/rss+xml" />

    <item>
      <title>Measuring and reclaiming Postgres table bloat</title>
      <link>https://insightral.com/blog/postgres-table-bloat</link>
      <guid isPermaLink="true">https://insightral.com/blog/postgres-table-bloat</guid>
      <pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate>
      <description>Table bloat is dead tuple accumulation that VACUUM has not yet reclaimed. At scale it inflates table size, slows sequential scans, and wastes I/O budget.</description>
    </item>

    <item>
      <title>Why autovacuum stops running and how to diagnose it</title>
      <link>https://insightral.com/blog/postgresql-autovacuum-not-running</link>
      <guid isPermaLink="true">https://insightral.com/blog/postgresql-autovacuum-not-running</guid>
      <pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate>
      <description>Autovacuum not running means dead tuples accumulating, table bloat growing, and eventually query plans degrading. Here is how to find out why it stopped.</description>
    </item>

    <item>
      <title>What &quot;idle in transaction&quot; sessions mean and how to fix them</title>
      <link>https://insightral.com/blog/postgres-idle-in-transaction</link>
      <guid isPermaLink="true">https://insightral.com/blog/postgres-idle-in-transaction</guid>
      <pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate>
      <description>An &quot;idle in transaction&quot; session is a transaction that was opened and never closed. It holds locks, blocks autovacuum, and can stall your entire database.</description>
    </item>

    <item>
      <title>Troubleshooting slow queries on Supabase</title>
      <link>https://insightral.com/blog/supabase-slow-query-troubleshooting</link>
      <guid isPermaLink="true">https://insightral.com/blog/supabase-slow-query-troubleshooting</guid>
      <pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate>
      <description>Supabase wraps Postgres with RLS, connection pooling, and branching — each of which adds failure modes that standard Postgres debugging guides miss. This is the actual troubleshooting path.</description>
    </item>

    <item>
      <title>Finding missing indexes in Postgres with pg_stat_user_tables</title>
      <link>https://insightral.com/blog/postgres-missing-index-detection</link>
      <guid isPermaLink="true">https://insightral.com/blog/postgres-missing-index-detection</guid>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <description>A table doing 50,000 sequential scans per hour with 2 million rows is a maintenance ticket waiting to happen. Here&apos;s how to find those tables before they become incidents.</description>
    </item>

    <item>
      <title>How to diagnose and fix Postgres connection pool exhaustion</title>
      <link>https://insightral.com/blog/postgres-connection-pool-exhausted</link>
      <guid isPermaLink="true">https://insightral.com/blog/postgres-connection-pool-exhausted</guid>
      <pubDate>Wed, 20 May 2026 00:00:00 GMT</pubDate>
      <description>When pg_stat_activity fills up and new connections start timing out, the fix is rarely &apos;raise max_connections&apos;. Here&apos;s the actual diagnosis path.</description>
    </item>
  </channel>
</rss>