Re: CREATE DATABASE command for non-libc providers - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: CREATE DATABASE command for non-libc providers
Date
Msg-id 4d8a8e2999408ca5ca8f92edde241214113060e2.camel@j-davis.com
Whole thread Raw
In response to Re: CREATE DATABASE command for non-libc providers  ("Daniel Verite" <daniel@manitou-mail.org>)
Responses Re: CREATE DATABASE command for non-libc providers
List pgsql-hackers
On Tue, 2025-06-10 at 23:44 +0200, Daniel Verite wrote:
> I may miss something, but I don't see a
> technical reason why this code could not be taught to call the
> equivalent
> functions of the current collation provider, following the same
> principles
> as the regex code.

The main challenge is backwards compatibility. Users of FTS would need
to recreate all of their tsvectors and indexes dependent on them. It's
even possible that some users only have tsvectors and don't store the
original data in the database, which would further complicate matters.

We could try to create a GUC to control this behavior, but behavior-
changing GUCs don't have a great history, and it would probably last
quite some time before we could really turn off libc for good.

There would be similar challenges for downcase_identifier() and maybe
pg_strcasecmp().

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Improve tab completion for COPY
Next
From: Daniil Davydov
Date:
Subject: Re: [BUG] Cannot flush buffers of temp table deleted from other session