| 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-08 06:21:58 |
| Message-ID: | 1898b923-b882-5954-94a8-15b493a12af3@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04.03.23 19:29, Jeff Davis wrote:
> It looks like the way you've handled this is by inserting the collation
> with collprovider=icu even if built without ICU support. I think that's
> a new case, so we need to make sure it throws reasonable user-facing
> errors.
It would look like this:
=> select * from t1 order by b collate unicode;
ERROR: 0A000: ICU is not supported in this build
> I do like your approach though because, if someone is using a standard
> collation, I think "not built with ICU" (feature not supported) is a
> better error than "collation doesn't exist". It also effectively
> reserves the name "unicode".
right
| From | Date | Subject | |
|---|---|---|---|
| Next Message | houzj.fnst@fujitsu.com | 2023-03-08 06:51:07 | RE: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher |
| Previous Message | Michael Paquier | 2023-03-08 06:19:33 | Re: Normalization of utility queries in pg_stat_statements |