Re: [HACKERS] What users can do with custom ICU collations inPostgres 10 - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] What users can do with custom ICU collations inPostgres 10
Date
Msg-id 3862d484-f0a5-9eef-c54e-3f6808338726@2ndquadrant.com
Whole thread Raw
In response to [HACKERS] What users can do with custom ICU collations in Postgres 10  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: [HACKERS] What users can do with custom ICU collations inPostgres 10  (Peter Geoghegan <pg@bowt.ie>)
Re: [HACKERS] What users can do with custom ICU collations inPostgres 10  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On 8/9/17 18:49, Peter Geoghegan wrote:
> There are actually very many customizations to collations that are
> possible beyond what the "stock" ICU collations provide (whatever
> "stock" means).

This is very nice indeed, and I was not aware that this was possible
with what we already have in place.

I'm having trouble finding some concrete documentation for this.  The TR
35 link you showed documents the key words and values, BCP 47 documents
the syntax, but nothing puts it all together in a form consumable by
users.  The ICU documentation still mainly focuses on the "old"
@keyword=value syntax.  I guess we'll have to write our own for now.

Given that we cannot reasonably preload all these new variants that you
demonstrated, I think it would make sense to drop all the keyword
variants from the preloaded set.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] shared memory based stat collector (was: Sharingrecord typmods between backends)
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] shared memory based stat collector (was: Sharing record typmods between backends)