| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Subject: | Re: [17] collation provider "builtin" |
| Date: | 2023-12-29 18:42:18 |
| Message-ID: | 74712d97c9cdf014c8a34afa22b948a2e85ec69b.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2023-06-15 at 15:08 -0400, Joe Conway wrote:
> > I haven't studied the details yet but +1 for this idea. It models
> > what we are actually doing.
>
> +1 agreed
I am combining this discussion with my "built-in CTYPE provider"
proposal here:
https://www.postgresql.org/message-id/804eb67b37f41d3afeb2b6469cbe8bfa79c562cc.camel@j-davis.com
and the most recent patch is posted there. Having a built-in provider
is more useful if it also offers a "C.UTF-8" locale that is superior to
the libc locale of the same name.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2023-12-29 19:14:46 | Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs |
| Previous Message | Tom Lane | 2023-12-29 18:38:07 | Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs |