<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Database on Experiment, Fail, Learn, Repeat</title>
    <link>https://www.hairizuan.com/categories/database/</link>
    <description>Recent content in Database on Experiment, Fail, Learn, Repeat</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2026 Hairizuan Noorazman</copyright>
    <lastBuildDate>Sat, 29 Aug 2026 21:48:12 +0800</lastBuildDate><atom:link href="https://www.hairizuan.com/categories/database/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>UUIDv4, UUIDv7, and Avoiding Deep OFFSET Pagination</title>
      <link>https://www.hairizuan.com/uuidv4-uuidv7-and-avoiding-deep-offset-pagination/</link>
      <pubDate>Sat, 01 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/uuidv4-uuidv7-and-avoiding-deep-offset-pagination/</guid>
      <description>&lt;p&gt;I initially thought UUIDv7 would be very important for avoiding expensive &lt;code&gt;OFFSET&lt;/code&gt; pagination. UUIDv7 is time ordered, while UUIDv4 is random, so it seemed natural that changing the identifier would be the key to fast pagination.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>PostgreSQL MVCC and Autovacuum Learnings</title>
      <link>https://www.hairizuan.com/postgresql-mvcc-and-autovacuum-learnings/</link>
      <pubDate>Fri, 31 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/postgresql-mvcc-and-autovacuum-learnings/</guid>
      <description>&lt;p&gt;PostgreSQL can let readers and writers work concurrently because of multi-version concurrency control, or MVCC. The trade-off is that an update usually creates a new tuple version instead of replacing the old one in place. A delete also makes a tuple obsolete without immediately removing its storage.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Initial PostgreSQL Index Optimization Lessons</title>
      <link>https://www.hairizuan.com/initial-postgresql-index-optimization-lessons/</link>
      <pubDate>Wed, 01 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/initial-postgresql-index-optimization-lessons/</guid>
      <description>&lt;p&gt;I built a small Go CRUD service to learn where a PostgreSQL-backed application starts to slow down. The service manages companies, users, and inventory, while a separate load generator creates a repeatable mixture of reads and writes.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
