| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org, Daniel Verite <daniel(at)manitou-mail(dot)org>, Noah Misch <noah(at)leadboat(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeremy Schneider <schneider(at)ardentperf(dot)com> |
| Subject: | Re: [18] Policy on IMMUTABLE functions and Unicode updates |
| Date: | 2024-07-24 04:42:26 |
| Message-ID: | cf51cfa1-5fce-4f9b-acb4-81f517ba05b1@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 24.07.24 03:37, Robert Haas wrote:
> On Tue, Jul 23, 2024 at 4:36 PM Peter Eisentraut <peter(at)eisentraut(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nisha Moond | 2024-07-24 04:50:24 | Re: Conflict detection and logging in logical replication |
| Previous Message | Richard Guo | 2024-07-24 04:12:13 | Re: apply_scanjoin_target_to_paths and partitionwise join |