Re: Change initdb default to the builtin collation provider

From: Anders Åstrand <anders(at)449(dot)se>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Change initdb default to the builtin collation provider
Date: 2026-03-12 06:44:33
Message-ID: 7130016e-848f-4cf8-83a1-4df6bf795e95@449.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> And, on a personal level, I have a hard time understanding why anyone
> would be OK with a sort order that puts Álvaro after Zebra instead of
> between Alvaro and Beatriz, because that seems extremely frustrating.

And I would find it extremly frustrating if Åstrand was sorted between
Alvaro and Beatriz instead of after Zebra where it belongs.

This is kind of the point. There is no generally correct way to sort
alphabetically, which is why we should force anyone wanting to do so to
make an active choice about which rules should be used. I think a
default that's obviously wrong is better than a default that's subtly
wrong in this case.

--
Anders Åstrand
Percona

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2026-03-12 07:00:19 Re: POC: PLpgSQL FOREACH IN JSON ARRAY
Previous Message Chao Li 2026-03-12 06:37:56 Re: ALTER TABLE: warn when actions do not recurse to partitions