| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | more Unicode data updates |
| Date: | 2019-06-19 20:34:24 |
| Message-ID: | 77f69366-ca31-6437-079f-47fce69bae1b@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Correct-script-name-in-README-file.patch | text/plain | 911 bytes |
| 0002-Make-script-output-more-pgindent-compatible.patch | text/plain | 1.0 KB |
| 0003-Update-unicode_norm_table.h-to-Unicode-12.1.0.patch | text/plain | 183.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2019-06-19 20:42:54 | Re: pg_upgrade: Improve invalid option handling |
| Previous Message | Alvaro Herrera | 2019-06-19 20:08:44 | Re: Race conditions with TAP test for syncrep |