| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)ru> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, AndrewBille(at)gmail(dot)com, peter(dot)eisentraut(at)enterprisedb(dot)com |
| Subject: | Re: ICU for global collation |
| Date: | 2022-09-16 02:28:09 |
| Message-ID: | YyPfOTUT50q88mu8@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 14, 2022 at 05:19:34PM +0300, Marina Polyakova wrote:
> I was surprised that it is allowed to create clusters/databases where the
> default ICU collations do not actually work due to unsupported encodings:
>
> $ initdb --encoding SQL_ASCII --locale-provider icu --icu-locale en-US -D
> data &&
> pg_ctl -D data -l logfile start &&
> psql -c "SELECT 'a' < 'b'" template1
> ...
> waiting for server to start.... done
> server started
> ERROR: encoding "SQL_ASCII" not supported by ICU
>
> $ createdb --encoding SQL_ASCII --locale-provider icu --icu-locale en-US
> --template template0 mydb &&
> psql -c "SELECT 'a' < 'b'" mydb
> ERROR: encoding "SQL_ASCII" not supported by ICU
>
> The patch diff_check_icu_encoding.patch prohibits the creation of such
> objects...
Agreed that it is a bit confusing to get this type of error after the
database has been created when querying it due to a mix of unsupported
options. Peter?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | bt22kawamotok | 2022-09-16 02:46:14 | Re: [PATCH]Feature improvement for MERGE tab completion |
| Previous Message | Michael Paquier | 2022-09-16 02:22:46 | Re: pg_basebackup's --gzip switch misbehaves |