Re: Update Unicode data to Unicode 16.0.0
От | Jeff Davis |
---|---|
Тема | Re: Update Unicode data to Unicode 16.0.0 |
Дата | |
Msg-id | 0e05b887fa556271fd7872c3dfc8b6da32b1518f.camel@j-davis.com обсуждение исходный текст |
Ответ на | Re: Update Unicode data to Unicode 16.0.0 (Laurenz Albe <laurenz.albe@cybertec.at>) |
Ответы |
Re: Update Unicode data to Unicode 16.0.0
|
Список | 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 по дате отправления: