<?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 darek.dk</title>
    <link>https://darek.dk/categories/database/</link>
    <description>Recent content in Database on darek.dk</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>darek.dk</copyright>
    <lastBuildDate>Wed, 12 Mar 2025 17:17:17 +0000</lastBuildDate>
    <atom:link href="https://darek.dk/categories/database/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PostgreSQL 17 Collation Changes: Why It Broke Everything</title>
      <link>https://darek.dk/posts/2025-03-12-postgresql-17-collation-breaking-change/</link>
      <pubDate>Wed, 12 Mar 2025 17:17:17 +0000</pubDate>
      <guid>https://darek.dk/posts/2025-03-12-postgresql-17-collation-breaking-change/</guid>
      <description>If you&amp;rsquo;ve recently upgraded to PostgreSQL 17 and suddenly started seeing errors about colliculocale not existing, you&amp;rsquo;re not alone. This column was quietly renamed to colllocale in commit f696c0cd, breaking queries that relied on the old name.&#xA;Now, any code that referenced pg_collation.colliculocale throws errors because the column is just gone. Developers are left with two choices: update their queries or stick with an older PostgreSQL version.&#xA;For example, a query like this:</description>
    </item>
  </channel>
</rss>
