<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>TOAST on Nalar</title>
    <link>https://nalar.dev/tags/toast/</link>
    <description>Recent content in TOAST on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 15 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/toast/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PostgreSQL TOAST Moves Large Values Outside Heap Rows</title>
      <link>https://nalar.dev/postgresql-toast-moves-large-values-outside-heap-rows/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/postgresql-toast-moves-large-values-outside-heap-rows/</guid>
      <description>&lt;h1 id=&#34;postgresql-toast-moves-large-values-outside-heap-rows&#34;&gt;PostgreSQL TOAST Moves Large Values Outside Heap Rows&lt;/h1&gt;&#xA;&lt;p&gt;PostgreSQL heap tuples cannot span data pages. A row containing a large &lt;code&gt;text&lt;/code&gt;, &lt;code&gt;bytea&lt;/code&gt;, &lt;code&gt;jsonb&lt;/code&gt;, or other variable-length value therefore cannot simply continue onto the next heap page. TOAST provides the storage mechanism that keeps such rows representable: eligible values can be compressed, moved out of line, or both.&lt;/p&gt;&#xA;&lt;p&gt;The visible SQL value does not change when this happens. The physical representation does. A heap tuple may contain a compact reference while the value&amp;rsquo;s bytes reside as chunk rows in a separate relation associated with the table.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
