From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add standard collation UNICODE |
Date: | 2023-03-09 10:21:25 |
Message-ID: | e44e28ca-fce3-00c1-9d7c-753cac301b30@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 08.03.23 19:25, Jeff Davis wrote:
> Why is "unicode" only provided for the UTF-8 encoding? For "ucs_basic"
> that makes some sense, because the implementation only works in UTF-8.
> But here we are using ICU, and the "und" locale should work for any
> ICU-supported encoding. I suggest that we use collencoding=-1 for
> "unicode", and the docs can just add a note next to "ucs_basic" that it
> only works for UTF-8, because that's the weird case.
make sense
> For the docs, I suggest that you clarify that "ucs_basic" has the same
> behavior as the C locale does *in the UTF-8 encoding*. Not all users
> might pick up on the subtlety that the C locale has different behaviors
> in different encodings.
Ok, word-smithed a bit more.
How about this patch version?
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Add-standard-collation-UNICODE.patch | text/plain | 3.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-03-09 10:29:47 | Re: Allow tests to pass in OpenSSL FIPS mode |
Previous Message | Daniel Gustafsson | 2023-03-09 10:01:57 | Re: Raising the SCRAM iteration count |