Re: Collation version tracking for macOS
От | Jeremy Schneider |
---|---|
Тема | Re: Collation version tracking for macOS |
Дата | |
Msg-id | 171D0968-0F8D-4522-B348-19D683364D9E@ardentperf.com обсуждение исходный текст |
Ответ на | Re: Collation version tracking for macOS (Thomas Munro <thomas.munro@gmail.com>) |
Ответы |
Re: Collation version tracking for macOS
|
Список | pgsql-hackers |
> On Jun 8, 2022, at 03:19, Thomas Munro <thomas.munro@gmail.com> wrote: > > On Wed, Jun 8, 2022 at 12:23 PM Peter Geoghegan <pg@bowt.ie> wrote: >> ISTM that there are two mostly-distinct questions here: >> >> 1. How do we link to multiple versions of ICU at the same time, in a >> way that is going to work smoothly on mainstream platforms? >> > Yeah. Well I couldn't resist doing some (very!) experimental hacking. > See attached. Even if PG supports two versions of ICU, how does someone actually go about removing every dependency on the old versionand replacing it with the new? Can it be done without downtime? Can it be done without modifying a running application?Avoiding “collate” clauses on SQL statements requires working behind the scenes with defaults and indexes andpartitions and constraints and everything else. I’m having a hard time coming up with a way this would be possible inpractice, with all the places collations can show up. Is the idea of “alter database” to change the default collation even realistic? I’m having a bit of trouble picturing what the end game is here -Jeremy Sent from my TI-83
В списке pgsql-hackers по дате отправления: