Re: Order changes in PG16 since ICU introduction

>> As I replied in that subthread, that creates a worse problem: if you
>> only change the provider when the locale is C, then what about when the
>> locale is *not* C?
>> 
>>   export LANG=en_US.UTF-8
>>   initdb -D data --locale=fr_FR.UTF-8
>>   ...
>>     provider:    icu
>>     ICU locale:  en-US
>> 
>> I believe that case is an order of magnitude worse than the other cases
>> you brought up in that subthread.
>> 
>> It also leaves the fundamental problem in place that LOCALE only
>> applies to the libc provider, which multiple people have agreed is not
>> acceptable.

Note that most of PostgreSQL users in Japan do initdb
--no-locale. Almost never use other than C locale because the users do
not rely on system collation. Most database have an extra column which
represents the pronunciation in Hiragana or Katakana.

Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp