<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Postgres on Percona Community</title><link>https://percona.community/events_tag/postgres/</link><description>Recent content in Postgres on Percona Community</description><generator>Hugo</generator><language>en-us</language><copyright>© Percona Community. MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.</copyright><lastBuildDate>Tue, 07 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://percona.community/events_tag/postgres/index.xml" rel="self" type="application/rss+xml"/><item><title>Nightmare on Collation Street - April 7, 2026</title><link>https://percona.community/events/2026-nightmare-on-collation-street/</link><pubDate>Tue, 07 Apr 2026 00:00:00 +0000</pubDate><guid>https://percona.community/events/2026-nightmare-on-collation-street/</guid><description>&lt;p>Character collations - the rules for comparing and sorting character strings - are not universal, even languages which use the same characters may sort them differently. These rules may also not be stable, and the libraries implementing them may have errors, requiring fixes and updates. When character string data is indexed or partitioned under one set of rules, then queried under another, it may create some problems.&lt;/p>
&lt;p>Join Jan and Alastair for a discussion about how this becomes your Postgres database’s problem, when it may come for you, and how to avoid trouble. We’ll give you one spoiler, running upstairs is no more useful here than in any slasher movie.&lt;/p></description></item></channel></rss>