Re: Update Unicode data to Unicode 16.0.0 - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Update Unicode data to Unicode 16.0.0
Date
Msg-id 0e05b887fa556271fd7872c3dfc8b6da32b1518f.camel@j-davis.com
Whole thread Raw
In response to Re: Update Unicode data to Unicode 16.0.0  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Update Unicode data to Unicode 16.0.0
List pgsql-hackers
On Tue, 2024-11-12 at 10:40 +0100, Laurenz Albe wrote:
> I want to reiterate what I said in the above thread:
> If that means that indexes on strings using the "builtin" collation
> provider need to be reindexed after an upgrade, I am very much
> against it.

How would you feel if there was a better way to "lock down" the
behavior using an extension?

I have a patchset here:

https://www.postgresql.org/message-id/78a1b434ff40510dc5aaabe986299a09f4da90cf.camel%40j-davis.com

that changes the implementation of collation and ctype to use method
tables rather than branching, and it also introduces some hooks that
can be used to replace the method tables with whatever you want.

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Interrupts vs signals
Next
From: Masahiko Sawada
Date:
Subject: Re: Fix an error while building test_radixtree.c with TEST_SHARED_RT