Re: [17] collation provider "builtin"

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [17] collation provider "builtin"
Date: 2023-06-14 23:20:30
Message-ID: CA+hUKGKZQ8ysmqCGTTWA6ahGfd2UvDd-x3gEoGMk6drZHRJDAA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2023-06-14 23:56:55 Re: Inconsistent results with libc sorting on Windows
Previous Message Jeff Davis 2023-06-14 22:55:05 [17] collation provider "builtin"