public inbox for pgsql-general@postgresql.org  

help / color / mirror / Atom feed

From: Daniel Verite <daniel@manitou-mail.org>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Choosing default collation/ctype
Date: Tue, 05 May 2026 20:28:43 +0200
Message-ID: <555d1594-87fd-44ef-be4d-ef001ef5d2e1@manitou-mail.org> (raw)
In-Reply-To: <7a6954c2dfe3f224b4c45aa59f7fb6e951ce93b0.camel@cybertec.at>

	Laurenz Albe wrote:

> But if you are using "C.UTF-8", the semantics of upper() can change
> between versions, if Unicode is upgraded. 

Oh I see. Sure, "C" is not affected by that.

> That bears a residual risk
> of OS upgrades breaking indexes on upper(col).

OS upgrades don't count in the case of the builtin provider, but
major Postgres upgrades, yes.

> I'd say that the small benefit of better case conversion isn't worth
> the risk.  I'd chose "C", and use a natural language collation explicitly
> on columns where these things matter.

While I understanding the reasoning, I'm of the opposite opinion.
To me the lack of Unicode support in "C" is too annoying to make
it a blanket recommendation as the default locale.


Best regards,
-- 
Daniel Vérité 
https://postgresql.verite.pro/

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-general@postgresql.org
  Cc: daniel@manitou-mail.org, laurenz.albe@cybertec.at, ronljohnsonjr@gmail.com, pgsql-general@lists.postgresql.org
  Subject: Re: Choosing default collation/ctype
  In-Reply-To: <555d1594-87fd-44ef-be4d-ef001ef5d2e1@manitou-mail.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox