| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: What users can do with custom ICU collations in Postgres 10 |
| Date: | 2017-08-15 18:19:43 |
| Message-ID: | 9ff6fc17-497c-3c98-359f-f4583abc4bf3@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/14/17 12:15, Peter Eisentraut wrote:
> 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.
After playing with this a bit, I'm having some doubts. While the "k"
keys from TR 35 are algorithmic parameters that apply to all locales and
can be looked up in the respective documents, I don't find any way a
user can discover what collation types ("co") are available for a
locale. Any ideas? If there isn't one, I think we need to provide one.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-08-15 18:33:56 | Re: What users can do with custom ICU collations in Postgres 10 |
| Previous Message | Robert Haas | 2017-08-15 17:54:04 | Re: [PATCH] pageinspect function to decode infomasks |