Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: ICU for global collation
From: "Daniel Verite" <daniel@manitou-mail.org>
To: "Julien Rouhaud" <rjuju123@gmail.com>
Cc: Peter Eisentraut
 <peter.eisentraut@enterprisedb.com>,
 Pgsql-Hackers <pgsql-hackers@postgresql.org>
In-Reply-To: <YdxNVzIN8rwklXsE@jrouhaud>
Date: Tue, 11 Jan 2022 12:36:46 +0100
Message-Id: <8647718d-eecb-4a4b-9929-7cb16eae8764@manitou-mail.org>
Archived-At: 
 <https://www.postgresql.org/message-id/8647718d-eecb-4a4b-9929-7cb16eae8764%40manitou-mail.org>
Precedence: bulk

	Julien Rouhaud wrote:

> > I guess there's still the possibility of requiring that the ICU db-wide
> > collation of the new database does exist in the template database,
> > and then the CREATE DATABASE would refer to that collation instead of
> > an independent locale string.
>=20
> That could work.  However if having the collation in the template databas=
e a
> strict requirement the something should also be done for initdb, and it w=
ill
> probably be a bigger problem.

If CREATE DATABASE referred to a collation in the template db,
either that collation already exists, or the user would have to add it
to the template db with CREATE COLLATION.
initdb already populates the template databases with a full set of
ICU collations through pg_import_system_collations().
I don't quite see what change you're seeing that would be needed in
initdb.


Best regards,
--=20
Daniel V=E9rit=E9
PostgreSQL-powered mailer: https://www.manitou-mail.org
Twitter: @DanielVerite