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/804eb67b
On Wed, 2023-06-14 at 15:55 -0700, Jeff Davis 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",
>
On Fri, 2023-06-16 at 16:01 +0200, Peter Eisentraut wrote:
> What happens if after this patch you continue to specify
> provider=libc
> and locale=C? Do you then get the "slow" path?
Users can continue to use the libc provider as they did before and the
fast path will still work.
> Should there
On 15.06.23 00:55, Jeff Davis 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
On 6/14/23 19:20, Thomas Munro wrote:
On Thu, Jun 15, 2023 at 10:55 AM Jeff Davis 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 coll
On Thu, Jun 15, 2023 at 10:55 AM Jeff Davis 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",
> whi
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
