Re: Choosing default collation/ctype - Mailing list pgsql-general

From Laurenz Albe
Subject Re: Choosing default collation/ctype
Date
Msg-id bdce746ad6052774fbc0de138e7c4fcc77886e77.camel@cybertec.at
Whole thread
In response to Re: Choosing default collation/ctype  ("Daniel Verite" <daniel@manitou-mail.org>)
Responses Re: Choosing default collation/ctype
List pgsql-general
On Mon, 2026-05-04 at 21:34 +0200, Daniel Verite wrote:
> Laurenz Albe wrote:
>
> > > Then choose UTF8.
> >
> > 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('été') is 'éTé' instead of 'ÉTÉ', and 'é' ~ '\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" .

Yes, "builtin" and the "C" collation is the best default value.

Yours,
Laurenz Albe



pgsql-general by date:

Previous
From: Matt Magoffin
Date:
Subject: Re: Confirmation on concurrent SELECT FOR UPDATE with ON CONFLICT DO NOTHING
Next
From: Igor Korot
Date:
Subject: Re: Choosing default collation/ctype