Re: [HACKERS] What users can do with custom ICU collations in Postgres 10

2017-08-21 Thread Peter Eisentraut
On 8/15/17 15:04, Peter Geoghegan wrote: > * "23.2.2.3. Copying Collations" suggests that the only use of CREATE > COLLATION is copying collations, which is far from true with ICU. We > should change that at the same time as this change is made. I think > that just changing the title would improve

Re: [HACKERS] What users can do with custom ICU collations in Postgres 10

2017-08-15 Thread Peter Geoghegan
On Tue, Aug 15, 2017 at 11:33 AM, Peter Eisentraut wrote: > On 8/9/17 18:49, Peter Geoghegan wrote: >> I'd like to give a demo on what is already possible, but not currently >> documented. I didn't see anyone else comment on this, including Peter >> E (maybe I missed that?). We should improve the

Re: [HACKERS] What users can do with custom ICU collations in Postgres 10

2017-08-15 Thread Peter Geoghegan
On Tue, Aug 15, 2017 at 11:19 AM, Peter Eisentraut wrote: > 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 playin

Re: [HACKERS] What users can do with custom ICU collations in Postgres 10

2017-08-15 Thread Peter Eisentraut
On 8/9/17 18:49, Peter Geoghegan wrote: > I'd like to give a demo on what is already possible, but not currently > documented. I didn't see anyone else comment on this, including Peter > E (maybe I missed that?). We should improve the documentation in this > area, to get this into the hands of user

Re: [HACKERS] What users can do with custom ICU collations in Postgres 10

2017-08-15 Thread Peter Eisentraut
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

Re: [HACKERS] What users can do with custom ICU collations in Postgres 10

2017-08-14 Thread Craig Ringer
On 15 August 2017 at 10:16, Michael Paquier wrote: > On Tue, Aug 15, 2017 at 11:10 AM, Craig Ringer > wrote: > > Ooh, this finally gives us a path toward case-insensitive default > database > > collation via CLDR caseLevel. > > > > http://userguide.icu-project.org/collation > > http://www.unicod

Re: [HACKERS] What users can do with custom ICU collations in Postgres 10

2017-08-14 Thread Michael Paquier
On Tue, Aug 15, 2017 at 11:10 AM, Craig Ringer wrote: > Ooh, this finally gives us a path toward case-insensitive default database > collation via CLDR caseLevel. > > http://userguide.icu-project.org/collation > http://www.unicode.org/reports/tr35/tr35-collation.html#Algorithm_Case > > That *defin

Re: [HACKERS] What users can do with custom ICU collations in Postgres 10

2017-08-14 Thread Craig Ringer
On 10 August 2017 at 06: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). Some of these are really cool, and I can imagine use > cases where they are very compelling

Re: [HACKERS] What users can do with custom ICU collations in Postgres 10

2017-08-14 Thread Peter Geoghegan
On Mon, Aug 14, 2017 at 9:15 AM, Peter Eisentraut wrote: > 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 doc

Re: [HACKERS] What users can do with custom ICU collations in Postgres 10

2017-08-14 Thread Peter Eisentraut
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