Re: [17] collation provider "builtin" - Mailing list pgsql-hackers

From Joe Conway
Subject Re: [17] collation provider "builtin"
Date
Msg-id 204ba69f-7027-f381-ade4-9aa38df9dbf3@joeconway.com
Whole thread Raw
In response to Re: [17] collation provider "builtin"  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: [17] collation provider "builtin"
List pgsql-hackers
On 6/14/23 19:20, Thomas Munro wrote:
> On Thu, Jun 15, 2023 at 10:55 AM Jeff Davis <pgsql@j-davis.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




pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: psql: Add role's membership options to the \du+ command
Next
From: Konstantin Knizhnik
Date:
Subject: Re: Let's make PostgreSQL multi-threaded