Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sPhXb-005qT3-DK for pgsql-hackers@arkaria.postgresql.org; Fri, 05 Jul 2024 11:55:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sPhXY-0095YQ-Nf for pgsql-hackers@arkaria.postgresql.org; Fri, 05 Jul 2024 11:55:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sPhXY-0095YI-EM for pgsql-hackers@lists.postgresql.org; Fri, 05 Jul 2024 11:55:49 +0000 Received: from dverite2024.planet-service.net ([185.16.44.252] helo=mail.verite.pro) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sPhXV-000WeN-Pr for pgsql-hackers@postgresql.org; Fri, 05 Jul 2024 11:55:47 +0000 Received: by mail.verite.pro (Postfix, from userid 1000) id C11DB2C849D; Fri, 5 Jul 2024 13:55:42 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-15" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: Built-in CTYPE provider From: "Daniel Verite" To: "Noah Misch" Cc: Peter Eisentraut , Jeff Davis , Robert Haas , Jeremy Schneider , pgsql-hackers@postgresql.org In-Reply-To: <20240702230333.8d.nmisch@google.com> Date: Fri, 05 Jul 2024 13:55:40 +0200 Message-Id: <41c3fa3f-e0bf-4d79-8af3-ef2fd7d56c2e@manitou-mail.org> X-Mailer: Manitou v1.7.3 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Noah Misch wrote: > > I don't think the builtin locale provider is any different in this resp= ect > > from the other providers: The locale data might change and there is a > > version mechanism to track that. We don't prevent pg_upgrade in scenar= ios > > like that for other providers. >=20 > Each packager can choose their dependencies so the v16 providers don't ha= ve > the problem. With the $SUBJECT provider, a packager won't have that opti= on. The Unicode data files downloaded into src/common/unicode/ depend on the versions defined in Makefile.global.in: # Unicode data information # Before each major release, update these and run make update-unicode. # Pick a release from here: . Note # that the most recent release listed there is often a pre-release; # don't pick that one, except for testing. UNICODE_VERSION =3D 15.1.0 # Pick a release from here: CLDR_VERSION =3D 45 (CLDR_VERSION is apparently not used yet). When these versions get bumped, it seems like packagers could stick to previous versions by just overriding these. When doing that, are there any function that may have an immutability breakage problem with the built-in locale provider? (I would expect none). Best regards, --=20 Daniel V=E9rit=E9 https://postgresql.verite.pro/ Twitter: @DanielVerite