Re: [17] collation provider "builtin"

From: Joe Conway <mail(at)joeconway(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [17] collation provider "builtin"
Date: 2023-06-15 19:08:45
Message-ID: 204ba69f-7027-f381-ade4-9aa38df9dbf3@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6/14/23 19:20, Thomas Munro wrote:
> On Thu, Jun 15, 2023 at 10:55 AM Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
>> The locale "C" (and equivalently, "POSIX") is not really a libc locale;
>> it's implemented internally with memcmp for collation and
>> pg_ascii_tolower, etc., for ctype.
>>
>> The attached patch implements a new collation provider, "builtin",
>> which only supports "C" and "POSIX". It does not change the initdb
>> default provider, so it must be requested explicitly. The user will be
>> guaranteed that collations with provider "builtin" will never change
>> semantics; therefore they need no version and indexes are not at risk
>> of corruption. See previous discussion[1].
>
> I haven't studied the details yet but +1 for this idea. It models
> what we are actually doing.

+1 agreed

--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Konstantin Knizhnik 2023-06-15 19:36:30 Re: Let's make PostgreSQL multi-threaded
Previous Message David G. Johnston 2023-06-15 18:47:56 Re: psql: Add role's membership options to the \du+ command