| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, "Jonathan S(dot)Katz" <jkatz(at)postgresql(dot)org> |
| Subject: | Re: EBCDIC sorting as a use case for ICU rules |
| Date: | 2023-07-06 09:35:41 |
| Message-ID: | 296a4a73-ee01-dfeb-30f4-05a0158b0efd@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 30.06.23 13:08, Daniel Verite wrote:
> About making a doc patch from this, I've came up with the attached,
> which generates a CREATE COLLATION statement with rules from an
> arbitrary strings that just lists characters in whichever order is desired.
I like adding more documentation and links around this. But I'm not
sure how this code you are including is supposed to help users
understand the rules language. Effectively, this would be adding
another rules mechanism on top of the existing one, but doesn't explain
either one.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2023-07-06 09:47:40 | RE: [PATCH] Reuse Workers and Replication Slots during Logical Replication |
| Previous Message | Peter Eisentraut | 2023-07-06 09:32:32 | Re: EBCDIC sorting as a use case for ICU rules |