Horton

Re: [18] Policy on IMMUTABLE functions and Unicode updates

Peter Eisentraut <peter@eisentraut.org>

View thread
From: Peter Eisentraut <peter@eisentraut.org>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, Jeff Davis <pgsql@j-davis.com>, pgsql-hackers@postgresql.org, Daniel Verite <daniel@manitou-mail.org>, Noah Misch <noah@leadboat.com>, Tom Lane <tgl@sss.pgh.pa.us>, Jeremy Schneider <schneider@ardentperf.com>
Date: 2024-07-24T04:42:26Z
Lists: 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.