Re: Built-in CTYPE provider

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Daniel Verite <daniel(at)manitou-mail(dot)org>, Jeremy Schneider <schneider(at)ardentperf(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Built-in CTYPE provider
Date: 2024-07-19 16:26:20
Message-ID: aa6e76ebbc405b0ac1b62efbbaea3c11236c4b0f.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2024-07-19 at 09:44 +0200, Laurenz Albe wrote:
> But the greatness of the step depends on our readiness to be careful
> with such changes.

You and Noah have been clear on that point, which is enough to make
*me* careful with any Unicode updates in the future. I'll suggest once
more that you say so in the policy thread here:

https://www.postgresql.org/message-id/d75d2d0d1d2bd45b2c332c47e3e0a67f0640b49c.camel%40j-davis.com

which would get broader visibility and I believe provide you with
stronger assurances that *everyone* will be careful with Unicode
updates.

Regards,
Jeff Davis

>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2024-07-19 16:59:56 Re: Incremental backup from a streaming replication standby fails
Previous Message Tom Lane 2024-07-19 16:22:14 Re: documentation structure