Re: ICU for global collation
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
On 07.01.22 10:03, Julien Rouhaud wrote: >> I changed the datcollate, datctype, and the new daticucoll fields to type >> text (from name). That way, the daticucoll field can be set to null if it's >> not applicable. Also, the limit of 63 characters can actually be a problem >> if you want to use some combination of the options that ICU locales offer. >> And for less extreme uses, having variable-length fields will save some >> storage, since typical locale names are much shorter. > > I understand the need to have daticucoll as text, however it's not clear to me > why this has to be changed for datcollate and datctype? IIUC those will only > ever contain libc-based collation and are still mandatory? Right. I just did this for consistency. It would be strange otherwise to have some fields as name and some as text. Arguably, using "name" here was wrong to begin with, since they are not really object names. Maybe there used to be a reason to avoid variable-length fields in pg_database, but there isn't one now AFAICT. > - pg_upgrade > > It checks (in check_locale_and_encoding()) the compatibility for each database, > and it looks like the daticucoll field should also be verified. Other than > that I don't think there is anything else needed for the pg_upgrade part as > everything else should be handled by pg_dump (I didn't look at the changes yet > given the below problems). Ok, I have added this and will include it in my next patch submission. > - CREATE DATABASE > - initdb Ok, some work is needed to make these interfaces behave sensibly in various combinations. I will look into that.
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add CHECK_FOR_INTERRUPTS while restoring changes during decoding.
- ce20f8b9f435 16.0 cited
-
Improve ICU option handling in CREATE DATABASE
- e59a67fb8fe1 16.0 landed
- 865b52af6104 15.0 landed
-
Don't allow creation of database with ICU locale with unsupported encoding
- c7db01e325a5 16.0 landed
- 148f66d59e2c 15.0 landed
-
Make locale option behavior more consistent
- da5d4ea5aaac 16.0 landed
- 3e694b318d20 15.0 landed
-
pg_dump: Dump colliculocale
- 72b6828da3f7 15.0 landed
- 396d348b046c 16.0 landed
-
Remove further unwanted linker flags from perl_embed_ldflags
- b4e936859dc4 16.0 cited
-
Doc: document possible need to raise kernel's somaxconn limit.
- 2c63b0930aee 15.0 cited
-
Reduce warnings with -Wshadow=compatible-local builds
- 92fce4e1eda9 16.0 cited
-
Remove redundant spaces in _outA_Expr() output
- 1c5818b9c68e 16.0 cited
-
Fix outdated --help message for postgres -f
- 63b64d827069 14.6 cited
-
pg_upgrade: Fix version comparison for global ICU support
- fa06a34d14ea 15.0 landed
-
Silence -Wmaybe-uninitialized compiler warning in dbcommands.c.
- 97bddda61b9a 15.0 landed
-
Add option to use ICU as global locale provider
- f2553d43060e 15.0 landed
-
DefineCollation() code cleanup
- e94bb1473eb3 15.0 landed
-
Change collate and ctype fields to type text
- 54637508f87b 15.0 landed
-
Call pg_newlocale_from_collation() also with default collation
- b99ccd2cb217 15.0 landed
-
Use libc version as a collation version on glibc systems.
- d5ac14f9ccdd 13.0 cited
-
Silence -Wmaybe-uninitialized compiler warnings in dbcommands.c.
- 3f6b3be39ca9 13.0 cited
-
Make LC_COLLATE and LC_CTYPE database-level settings. Collation and
- 61d967498802 8.4.0 cited