Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
From: "Daniel Verite" <daniel@manitou-mail.org>
To: "Laurenz Albe" <laurenz.albe@cybertec.at>
Cc: Ron Johnson <ronljohnsonjr@gmail.com>,
 pgsql-general@lists.postgresql.org
Subject: Re: Choosing default collation/ctype
In-Reply-To: <63e4b5165442ada9f187a0e14bbfe04795088bcd.camel@cybertec.at>
Date: Mon, 04 May 2026 21:34:00 +0200
Message-Id: <627add7e-94df-49ca-aa12-ae3900b7945f@manitou-mail.org>
Archived-At: <https://www.postgresql.org/message-id/627add7e-94df-49ca-aa12-ae3900b7945f%40manitou-mail.org>
Precedence: bulk

	Laurenz Albe wrote:

> > Then choose UTF8.
>=20
> Right!  And I recommend "C" for the collation.

Yet the "C" collation is unsuitable for handling character types
beyond ASCII.
For instance, it considers that accented letters are not letters,
so upper('=E9t=E9') is '=E9T=E9' instead of '=C9T=C9', and '=E9' ~ '\w' is =
false.

C.UTF-8 solves that, and since Postgres 17, it's available for all operating
systems with the builtin provider.
So if you target Postgres 17+, C.UTF-8 from the builtin provider is
a better choice for UTF-8 databases than "C" .


Best regards,
--=20
Daniel V=E9rit=E9=20
https://postgresql.verite.pro/