From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Move defaults toward ICU in 16? |
Date: | 2023-02-20 14:55:45 |
Message-ID: | 96ab0022-b629-2e99-9a4f-f1c886584cd3@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 17.02.23 21:43, Jeff Davis wrote:
>> select row_number() over (order by nazev collate "cs-x-icu"), nazev
>> from obce
>> except select row_number() over (order by nazev collate "cs_CZ"),
>> nazev from obce;
>>
>> returns a not empty set. So minimally for Czech collate, an index
>> rebuild is necessary
> Yes, that's true of any locale change, provider change, or even
> provider version change.
I'm confused. We are not going to try to change existing databases to a
different collation provider during pg_upgrade, are we?
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Lakhin | 2023-02-20 15:00:00 | Re: windows CI failing PMSignalState->PMChildFlags[slot] == PM_CHILD_ASSIGNED |
Previous Message | Peter Eisentraut | 2023-02-20 14:46:23 | Re: ICU locale validation / canonicalization |