Re: Collation version tracking for macOS - Mailing list pgsql-hackers

From Jeremy Schneider
Subject Re: Collation version tracking for macOS
Date
Msg-id 171D0968-0F8D-4522-B348-19D683364D9E@ardentperf.com
Whole thread Raw
In response to Re: Collation version tracking for macOS  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Collation version tracking for macOS
List 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 by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [PoC] Let libpq reject unexpected authentication requests
Next
From: Bharath Rupireddy
Date:
Subject: A proposal to force-drop replication slots to make disabling async/sync standbys or logical replication faster in production environments