<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>PostgreSQL 18 on Nalar</title>
    <link>https://nalar.dev/tags/postgresql-18/</link>
    <description>Recent content in PostgreSQL 18 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/postgresql-18/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PostgreSQL Virtual Generated Columns Compute Values at Read Time</title>
      <link>https://nalar.dev/postgresql-virtual-generated-columns-compute-values-at-read-time/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/postgresql-virtual-generated-columns-compute-values-at-read-time/</guid>
      <description>&lt;p&gt;PostgreSQL 18 can keep a generated column out of the stored row entirely. A virtual generated column evaluates its expression when the column is read, while a stored generated column evaluates on write and occupies storage like an ordinary column. PostgreSQL 18 also makes the virtual form the default when neither &lt;code&gt;VIRTUAL&lt;/code&gt; nor &lt;code&gt;STORED&lt;/code&gt; is specified.&lt;/p&gt;&#xA;&lt;p&gt;That distinction changes where computation occurs and which expressions PostgreSQL accepts. It also affects triggers, inheritance, partitioning, and logical replication.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
