Horton

Re: Built-in CTYPE provider

Daniel Verite <daniel@manitou-mail.org>

View thread View on postgr.es
From: "Daniel Verite" <daniel@manitou-mail.org>
To: "Noah Misch" <noah@leadboat.com>
Cc: Peter Eisentraut <peter@eisentraut.org>, Jeff Davis <pgsql@j-davis.com>, Robert Haas <robertmhaas@gmail.com>, Jeremy Schneider <schneider@ardentperf.com>, pgsql-hackers@postgresql.org
Date: 2024-07-05T11:55:40Z
Lists: pgsql-hackers 
	Noah Misch wrote:

> > I don't think the builtin locale provider is any different in this respect
> > 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 scenarios
> > like that for other providers.
> 
> Each packager can choose their dependencies so the v16 providers don't have
> the problem.  With the $SUBJECT provider, a packager won't have that option.

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: <https://www.unicode.org/Public/>.  Note
  # that the most recent release listed there is often a pre-release;
  # don't pick that one, except for testing.
  UNICODE_VERSION = 15.1.0

  # Pick a release from here: <http://cldr.unicode.org/index/downloads>
  CLDR_VERSION = 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,
-- 
Daniel Vérité
https://postgresql.verite.pro/
Twitter: @DanielVerite

Commits

  1. Support PG_UNICODE_FAST locale in the builtin collation provider.

  2. Support Unicode full case mapping and conversion.

  3. Fix test failures when language environment is not UTF-8.

  4. Add unicode_strtitle() for Unicode Default Case Conversion.

  5. Use version for builtin collations.

  6. Fix convert_case(), introduced in 5c40364dd6.

  7. Inline basic UTF-8 functions.

  8. Support C.UTF-8 locale in the new builtin collation provider.

  9. Fix another warning, introduced by 846311051e.

  10. Address more review comments on commit 2d819a08a1.

  11. Fix unreachable code warning from commit 2d819a08a1.

  12. Introduce "builtin" collation provider.

  13. Catalog changes preparing for builtin collation provider.

  14. Unicode case mapping tables and functions.

  15. Add Unicode property tables.

  16. Documentation update for Standard Collations.

  17. Cleanup for unicode-update build target and test.

  18. Shrink Unicode category table.

  19. Make some error strings more generic

  20. pg_upgrade: copy locale and encoding information to new cluster.

  21. Update Unicode data to Unicode 15.0.0

  22. Create a new type category for "internal use" types.