From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Matthias Apitz <gurucubano(at)googlemail(dot)com> |
Cc: | Dominique Devienne <ddevienne(at)gmail(dot)com>, Jeremy Schneider <schneider(at)ardentperf(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: COLLATION update in 13.1 |
Date: | 2025-02-24 15:10:06 |
Message-ID: | 56dbe5984c26ff2ebda5f3c607389a0416ae9d7f.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 2025-02-24 at 13:07 +0100, Matthias Apitz wrote:
> Thanks. I did \l before which gives:
>
> List of databases
> Name | Owner | Encoding | Collate | Ctype | ICU Locale | Locale Provider | Access privileges
> ------------+----------+----------+-------------+-------------+------------+-----------------+-----------------------
> bar | foo | UTF8 | de_DE.UTF-8 | de_DE.UTF-8 | | libc |
> customers | sisis | UTF8 | de_DE.UTF-8 | de_DE.UTF-8 | | libc |
> ...
>
> But why the ALTER statement needs the spelling different as the output of \l :
>
> sisis=# ALTER COLLATION "de_DE.UTF-8" REFRESH VERSION;
> ERROR: collation "de_DE.UTF-8" for encoding "UTF8" does not exist
>
> sisis=# ALTER COLLATION "de_DE.utf8" REFRESH VERSION;
> NOTICE: version has not changed
> ALTER COLLATION
Yes, that is annoying. You can use other collation names in CREATE DATABASE
than the ones in pg_collation. You have to choose the name that is used in
pg_collation, which is probably "de_DE.utf8".
Really, they refer to the same collation.
Yours,
Laurenz Albe
--
*E-Mail Disclaimer*
Der Inhalt dieser E-Mail ist ausschliesslich fuer den
bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat
dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte,
dass jede Form der Kenntnisnahme, Veroeffentlichung, Vervielfaeltigung oder
Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten Sie, sich
in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen.
*CONFIDENTIALITY NOTICE & DISCLAIMER
*This message and any attachment are
confidential and may be privileged or otherwise protected from disclosure
and solely for the use of the person(s) or entity to whom it is intended.
If you have received this message in error and are not the intended
recipient, please notify the sender immediately and delete this message and
any attachment from your system. If you are not the intended recipient, be
advised that any use of this message is prohibited and may be unlawful, and
you must not copy this message or attachment or disclose the contents to
any other person.
From | Date | Subject | |
---|---|---|---|
Next Message | Dominique Devienne | 2025-02-24 15:27:12 | Re: Keep specialized query pairs, or use single more general but more complex one |
Previous Message | Tom Lane | 2025-02-24 15:01:51 | Re: #XX000: ERROR: tuple concurrently updated |