| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Supporting non-deterministic collations with tailoring rules. |
| Date: | 2026-03-19 05:57:29 |
| Message-ID: | ca558d0f-cc8f-4afa-beb5-64c8fefb5c94@eisentraut.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18.03.26 19:21, Daniel Verite wrote:
> Peter Eisentraut wrote:
>
>> Ok, committed.
>>
>> Thoughts on backpatching? Seems like a straightforward bug fix.
>
> Thanks for pushing the patch!
> I thought it was not a candidate for backpatching because it's
> a collation change.
> Now, to have a problem with that change in a minor release,
> a user would need to have an ICU collation with a rule containing
> "[strength N]", where N<>3, even though it was ineffective (so
> either the user did not notice or they did but kept it
> nonetheless). Users who reported the problem hoped for a backpatch,
> but we cannot say there is zero risk with that change in a minor
> release. Personally I'm +0.
Ok, let's not then.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Postgress Cybrosys | 2026-03-19 05:57:31 | Fix type of 'reduction' variable in _bt_singleval_fillfactor() |
| Previous Message | JoongHyuk Shin | 2026-03-19 05:40:05 | pg_dump: fix NOT NULL constraint name comparison using makeObjectName |