From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Collation version tracking for macOS |
Date: | 2022-06-03 12:17:28 |
Message-ID: | ce1174ea-1942-37f0-421e-9ccff400dbcb@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 07.05.22 02:31, Thomas Munro wrote:
>> During development, I have been using the attached patch to simulate
>> libc collation versions on macOS. It just uses the internal major OS
>> version number. I don't know to what the extend the libc locales on
>> macOS are maintained or updated at all, so I don't know what practical
>> effect this would have. Again, it's mainly for development. If there
>> is interest from others, I think we could add this, maybe disabled by
>> default, or we just keep it in the mailing list archives for interested
>> parties.
> Last time I looked into this it seemed like macOS's strcoll() gave
> sensible answers in the traditional single-byte encodings, but didn't
> understand UTF-8 at all so you get C/strcmp() order. In other words
> there was effectively nothing to version.
Someone recently told me that collations in macOS have actually changed
recently and that this is a live problem. See explanation here:
So I think we should reconsider this patch, even for PG15.
From | Date | Subject | |
---|---|---|---|
Next Message | Jehan-Guillaume de Rorthais | 2022-06-03 13:42:32 | Self FK oddity when attaching a partition |
Previous Message | Daniel Gustafsson | 2022-06-03 12:01:18 | Re: [v15 beta] pg_upgrade failed if earlier executed with -c switch |