| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Subject: | Re: ICU for global collation |
| Date: | 2022-03-15 17:28:01 |
| Message-ID: | CA+Tgmobw227bwuHk6kwjriFQUofnZoAQhL1j3eYJyCcNO8u4MA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 15, 2022 at 12:58 PM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> On 14.03.22 19:57, Robert Haas wrote:
> > 1. What will happen if I set the ICU collation to something that
> > doesn't match the libc collation? How bad are the consequences?
>
> These are unrelated, so there are no consequences.
Can you please elaborate on this?
> > 2. If I want to avoid a mismatch between the two, then I will need a
> > way to figure out which libc collation corresponds to a given ICU
> > collation. How do I do that?
>
> You can specify the same name for both.
Hmm. If every name were valid in both systems, I don't think you'd be
proposing two fields.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2022-03-15 17:33:12 | pgsql: Add 'basebackup_to_shell' contrib module. |
| Previous Message | Ashutosh Sharma | 2022-03-15 17:26:31 | Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints |