<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>GiST on Nalar</title>
    <link>https://nalar.dev/tags/gist/</link>
    <description>Recent content in GiST on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/gist/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PostgreSQL Exclusion Constraints Block Overlapping Ranges</title>
      <link>https://nalar.dev/postgresql-exclusion-constraints-block-overlapping-ranges/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/postgresql-exclusion-constraints-block-overlapping-ranges/</guid>
      <description>&lt;p&gt;A unique constraint can reject two equal scalar values, but equality is too narrow for many scheduling and allocation rules. Two reservations can have different start and end timestamps while still occupying the same interval. PostgreSQL exclusion constraints express this kind of conflict directly in the database.&lt;/p&gt;&#xA;&lt;p&gt;An exclusion constraint compares pairs of rows with declared operators. A pair is rejected when every operator comparison in the constraint is true. This turns operators such as range overlap into enforceable cross-row rules without relying on a query followed by an insert.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
