Re: [18] Policy on IMMUTABLE functions and Unicode updates - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [18] Policy on IMMUTABLE functions and Unicode updates
Date
Msg-id cf51cfa1-5fce-4f9b-acb4-81f517ba05b1@eisentraut.org
Whole thread Raw
In response to Re: [18] Policy on IMMUTABLE functions and Unicode updates  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [18] Policy on IMMUTABLE functions and Unicode updates
List pgsql-hackers
On 24.07.24 03:37, Robert Haas wrote:
> On Tue, Jul 23, 2024 at 4:36 PM Peter Eisentraut <peter@eisentraut.org> wrote:
>> The sorting isn't the problem.  We have a versioning mechanism for
>> collations.  What we do with the version information is clearly not
>> perfect yet, but the mechanism exists and you can hack together queries
>> that answer the question, did anything change here that would affect my
>> indexes.  And you could build more tooling around that and so on.
> 
> In my experience, sorting is, overwhelmingly, the problem. What people
> complain about is that they do an upgrade - of PG or some OS package -
> and then their indexes are broken. Or their partition bounds are
> broken.

Fair enough.  My argument was, that topic is distinct from the topic of 
this thread.




pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: apply_scanjoin_target_to_paths and partitionwise join
Next
From: Nisha Moond
Date:
Subject: Re: Conflict detection and logging in logical replication