| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)ru>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, pryzby(at)telsasoft(dot)com, rjuju123(at)gmail(dot)com, daniel(at)manitou-mail(dot)org, AndrewBille(at)gmail(dot)com, michael(at)paquier(dot)xyz |
| Subject: | Re: ICU for global collation |
| Date: | 2022-09-17 04:58:36 |
| Message-ID: | 65ef1a8a-1fc3-3dc3-c7aa-6b9f649014b2@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16.09.22 08:49, Marina Polyakova wrote:
> But perhaps the check that --icu-locale cannot be specified unless
> locale provider icu is chosen should also be moved here? So all these
> checks will be in one place and it will use the provider from the
> template database (which could be icu):
>
> $ initdb --locale-provider icu --icu-locale en-US -D data &&
> pg_ctl -D data -l logfile start &&
> createdb --icu-locale ru-RU --template template0 mydb
> ...
> createdb: error: database creation failed: ERROR: ICU locale cannot be
> specified unless locale provider is ICU
Can you be more specific about what you are proposing here? I'm not
following.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2022-09-17 05:29:03 | introduce optimized linear search functions that return index of matching element |
| Previous Message | houzj.fnst@fujitsu.com | 2022-09-17 04:47:57 | RE: why can't a table be part of the same publication as its schema |