From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jeremy Schneider <schneider(at)ardentperf(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Built-in CTYPE provider |
Date: | 2023-12-20 19:13:12 |
Message-ID: | c04b690ed9f58eab01d2c298f62fe2a395eb4421.camel@j-davis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2023-12-20 at 13:49 +0100, Daniel Verite wrote:
> If the Postgres default was bytewise sorting+locale-agnostic
> ctype functions directly derived from Unicode data files,
> as opposed to libc/$LANG at initdb time, the main
> annoyance would be that "ORDER BY textcol" would no
> longer be the human-favored sort.
> For the presentation layer, we would have to write for instance
> ORDER BY textcol COLLATE "unicode" for the root collation
> or a specific region-country if needed.
> But all the rest seems better, especially cross-OS compatibity,
> truly immutable and faster indexes for fields that
> don't require linguistic ordering, alignment between Unicode
> updates and Postgres updates.
Thank you, that summarizes exactly the compromise that I'm trying to
reach.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2023-12-20 19:24:55 | Re: Built-in CTYPE provider |
Previous Message | Robert Haas | 2023-12-20 19:09:06 | Re: index prefetching |