Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o1Bwi-0000kb-8L for pgsql-hackers@arkaria.postgresql.org; Tue, 14 Jun 2022 19:11:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o1Bvi-00007U-Oi for pgsql-hackers@arkaria.postgresql.org; Tue, 14 Jun 2022 19:10:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o1Bvi-00007E-CF for pgsql-hackers@lists.postgresql.org; Tue, 14 Jun 2022 19:10:22 +0000 Received: from mail-qv1-xf29.google.com ([2607:f8b0:4864:20::f29]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1o1Bvf-0003Ug-FE for pgsql-hackers@postgresql.org; Tue, 14 Jun 2022 19:10:21 +0000 Received: by mail-qv1-xf29.google.com with SMTP id p31so5974925qvp.5 for ; Tue, 14 Jun 2022 12:10:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ardentperf-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:subject:from:in-reply-to:cc :date:message-id:references:to; bh=AaiERztIyu+EkyM7g4G9TjWWw4AJVW6EDJTAuEtof4I=; b=WXMTh7i3khOb5o2MybcqhwjBXaNvd8P82v6vaWiVNODijG/R5HoLqz2rihSysTs2/+ wDf3eQYybxVga8CjChRzM5EsGJ2OCUSU/mAIXbfZNKvozPhq3qv++gdfv1m58djQmKJo pxbOrsqn/BIbGBy8t28l0nMZJu8b8ETJ/ZV+PcKHmwoG4LxmRiAm43EVKL5AShPkmmpT tQveW6XfvLxBs2Bnb9ROEoO4svyUyKjTleD9G6H0IrgtBZNNPAF/hTq0UU8Va/60j+VE Nu8s6Frbb+6EWwEt1U5ZLlDYckQeqSty0uOd0g1Wn3pOeF90IPTbB1jX78qzlGyJ3l7J JPIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:cc:date:message-id:references:to; bh=AaiERztIyu+EkyM7g4G9TjWWw4AJVW6EDJTAuEtof4I=; b=qTDx1thlTJvKJzEBg5Pr2zRRtrPOOGIWYaLQloysnYOzq6HyreqQ/YoMouTiKCO5un JvFlaRIdna5Fjqp3ujwynRwOb1MQ7Wfwfs/LITja40KXsfNUl4E5owLAh9MqgcBOA8Ni dpsYrbdy15waKxiOOrsGW3Up2hpZw8PT5EDrRFzuuUNP9dMJGgVF/u3LBfkeLNzCg4rf /RZJr1cRNCJV+4UpFR6kegF3ArdsTFMvxwVbxpQkokTPT7elj+xQoOIQhZYMx6y/P8P0 pKTltjveoFJ7iqK+W8QlGd9PY6WYRHG6yop0DoesBaFgEXgYv+Pt/6kuirBCxnW6B4o0 kpBw== X-Gm-Message-State: AJIora/9TdIFE5SvI56ZlEOlrT9f6eOJK1ZITX2zlt/1IH4CyGU+8LgD HcJL/7nxTRDlZtHpEvBQj5/ZPA== X-Google-Smtp-Source: AGRyM1tvasBgQSWZ77HPAR9CSgIdhvia7G0bckBL+rBZhieGA1jHWaYgYlZsazbxJVe13EzDkJCOzQ== X-Received: by 2002:a05:6214:1c87:b0:46b:c547:543d with SMTP id ib7-20020a0562141c8700b0046bc547543dmr4670401qvb.52.1655233818287; Tue, 14 Jun 2022 12:10:18 -0700 (PDT) Received: from smtpclient.apple ([165.166.91.245]) by smtp.gmail.com with ESMTPSA id u21-20020ac858d5000000b00304e8938800sm7932158qta.96.2022.06.14.12.10.17 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 14 Jun 2022 12:10:17 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: Re: Collation version tracking for macOS From: Jeremy Schneider In-Reply-To: Cc: Peter Geoghegan , Thomas Munro , "Finnerty, Jim" , "Nasby, Jim" , Tom Lane , pgsql-hackers Date: Tue, 14 Jun 2022 15:10:16 -0400 Message-Id: References: To: Peter Eisentraut X-Mailer: iPhone Mail (19F77) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Jun 14, 2022, at 14:10, Peter Eisentraut wrote: > =EF=BB=BF > Conversely, why are we looking at the ICU version instead of the collation= version. If we have recorded the collation as being version 1234, we need t= o look through the available ICU versions (assuming we can load multiple one= s somehow) and pick the one that provides 1234. It doesn't matter whether i= t's the same ICU version that the collation was originally created with, as l= ong as the collation version stays the same. Does Unicode CDLR provide (or even track) versioning of collation or other i= 18n functionality for individual locale settings? I=E2=80=99m thinking it mi= ght not even have that concept in the original source repo/data, but I might= be remembering wrong. It would require not only watching for changes in the per-locale tailoring r= ules but also being cognizant of changes in root/DUCET behavior and understa= nding the impact of changes there. (Common mistake I=E2=80=99ve seen folks make when comparing OS glibc version= s is only looking at locale data, not realizing there have been changes to r= oot behavior that didn=E2=80=99t involve any changes to local data files) -Jeremy=