From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
cc: Thomas Munro <thomas.munro@gmail.com>,
        pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Collation version tracking for macOS
In-reply-to: <ce1174ea-1942-37f0-421e-9ccff400dbcb@enterprisedb.com>
References: <381977b1-0898-cb6f-a427-3b5d873e81bd@enterprisedb.com>
 <CA+hUKGKjkL=APm5nd3vGOtMAD_07nyvrbAaGaDduVD-EKM5Drw@mail.gmail.com>
 <ce1174ea-1942-37f0-421e-9ccff400dbcb@enterprisedb.com>
Comments: In-reply-to Peter Eisentraut <peter.eisentraut@enterprisedb.com>
	message dated "Fri, 03 Jun 2022 14:17:28 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <231071.1654273317.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 03 Jun 2022 12:21:57 -0400
Message-ID: <231072.1654273317@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/231072.1654273317%40sss.pgh.pa.us>
Precedence: bulk

Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
> On 07.05.22 02:31, Thomas Munro wrote:
>> 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:

> https://github.com/PostgresApp/PostgresApp/blob/master/docs/documentatio=
n/reindex-warning.md?plain=3D1#L66

> So I think we should reconsider this patch, even for PG15.

According to that document, they changed it in macOS 11, which came out
a year and a half ago.  Given the lack of complaints, it doesn't seem
like this is urgent enough to mandate a post-beta change that would
have lots of downside (namely, false-positive warnings for every other
macOS update).

			regards, tom lane