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>
Subject: Re: Order changes in PG16 since ICU introduction
To: "Tatsuo Ishii" <ishii@sraoss.co.jp>
Cc: pgsql@j-davis.com,
 Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
 andrew@tao11.riddles.org.uk,
 tgl@sss.pgh.pa.us,
 pgsql-hackers@lists.postgresql.org
In-Reply-To: <20230608.093033.648172765268838567.t-ishii@sranhm.sra.co.jp>
Date: Thu, 08 Jun 2023 11:03:25 +0200
Message-Id: <83ffec9f-b445-485c-9d64-b83ed314c85d@manitou-mail.org>
Archived-At: 
 <https://www.postgresql.org/message-id/83ffec9f-b445-485c-9d64-b83ed314c85d%40manitou-mail.org>
Precedence: bulk

	Tatsuo Ishii wrote:

> >> Yes it's a special case but when doing initdb --locale=3DC, a user does
> >> not need or want an ICU locale. They want the same thing than what v15
> >> does with the same arguments: a template0 database with
> >> datlocprovider=3D'c', datcollate=3D'C', datctype=3D'C', dateiculocale=
=3DNULL.
>=20
> So in this case the only way to keep the same behavior in v16 with "initdb
> --locale=3DC" (--no-locale) in v15 is, bulding PostgreSQL --without-icu?

AFAIK the --no-locale case in v16 is fixed since:

commit 5cd1a5af4d17496a58678c8eb7ab792119c2d723
Author: Jeff Davis <jdavis@postgresql.org>
Date:	Fri Apr 21 13:11:18 2023 -0700

    Fix initdb --no-locale.

    Discussion: https://postgr.es/m/878relf7cb.fsf@news-spur.riddles.org.uk
    Reported-by: Andrew Gierth


The --locale=3DC case is still being discussed. To me it should
produce the same result than --no-locale and --locale=3DC in v15, that is,
"ICU is the default" does not apply to that case, but currently
it initializes the cluster with an ICU locale.


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