more Unicode data updates
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t40809psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 28, 2026 at 04:03 AM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t40809_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t40809_1 && git checkout t40809_1Patchset v1 (message #1) is on t40809_1
src/include/common/unicode_norm_table.h also should be updated to the
latest Unicode tables, as described in src/common/unicode. See attached
patches. This also passes the tests described in
src/common/unicode/README. (That is, the old code does not pass the
current Unicode test file, but the updated code does pass it.)
I also checked contrib/unaccent/ but it seems up to date.
It seems to me that we ought to make this part of the standard major
release preparations. There is a new Unicode standard approximately
once a year; see <https://unicode.org/Public/>. (The 13.0.0 listed
there is not released yet.)
It would also be nice to unify and automate all these "update to latest
Unicode" steps.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachments:
t40809_10001-Correct-script-name-in-README-file.patchtext/plain; charset=UTF-8; name=0001-Correct-script-name-in-README-file.patch; x-mac-creator=0; x-mac-type=0Download+1-2
0002-Make-script-output-more-pgindent-compatible.patchtext/plain; charset=UTF-8; name=0002-Make-script-output-more-pgindent-compatible.patch; x-mac-creator=0; x-mac-type=0Download+2-2
0003-Update-unicode_norm_table.h-to-Unicode-12.1.0.patchtext/plain; charset=UTF-8; name=0003-Update-unicode_norm_table.h-to-Unicode-12.1.0.patch; x-mac-creator=0; x-mac-type=0Download+2017-1966
On Thu, Jun 20, 2019 at 8:35 AM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
src/include/common/unicode_norm_table.h also should be updated to the
latest Unicode tables, as described in src/common/unicode. See attached
patches. This also passes the tests described in
src/common/unicode/README. (That is, the old code does not pass the
current Unicode test file, but the updated code does pass it.)I also checked contrib/unaccent/ but it seems up to date.
It seems to me that we ought to make this part of the standard major
release preparations. There is a new Unicode standard approximately
once a year; see <https://unicode.org/Public/>. (The 13.0.0 listed
there is not released yet.)It would also be nice to unify and automate all these "update to latest
Unicode" steps.
+1, great idea. Every piece of the system that derives from Unicode
data should derive from the same version, and the version should be
mentioned in the release notes when it changes, and should be
documented somewhere centrally. I wondered about that when working on
the unaccent generator script but didn't wonder hard enough.
--
Thomas Munro
https://enterprisedb.com
On 2019-06-19 22:34, Peter Eisentraut wrote:
src/include/common/unicode_norm_table.h also should be updated to the
latest Unicode tables, as described in src/common/unicode. See attached
patches. This also passes the tests described in
src/common/unicode/README. (That is, the old code does not pass the
current Unicode test file, but the updated code does pass it.)
committed
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services