Re: [HACKERS] Can ICU be used for a database's default sort order?

2017-06-23 Thread Tom Lane
Peter Geoghegan writes: > On Fri, Jun 23, 2017 at 11:32 AM, Peter Eisentraut > wrote: >> 1) Associate by name only. That is, you can create a database with any >> COLLATION "foo" that you want, and it's only checked when you first >> connect to or

Re: [HACKERS] Can ICU be used for a database's default sort order?

2017-06-23 Thread Peter Geoghegan
On Fri, Jun 23, 2017 at 11:32 AM, Peter Eisentraut wrote: > It's something I hope to address soon. I hope you do. I think that we'd realize significant benefits by having ICU become the defacto standard collation provider, that most users get without even

Re: [HACKERS] Can ICU be used for a database's default sort order?

2017-06-23 Thread Peter Eisentraut
On 6/22/17 23:10, Peter Geoghegan wrote: > On Thu, Jun 22, 2017 at 7:10 PM, Tom Lane wrote: >> Is there some way I'm missing, or is this just a not-done-yet feature? > > It's a not-done-yet feature. It's something I hope to address soon. The main definitional challenge is

Re: [HACKERS] Can ICU be used for a database's default sort order?

2017-06-22 Thread Peter Geoghegan
On Thu, Jun 22, 2017 at 7:10 PM, Tom Lane wrote: > Is there some way I'm missing, or is this just a not-done-yet feature? It's a not-done-yet feature. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

[HACKERS] Can ICU be used for a database's default sort order?

2017-06-22 Thread Tom Lane
I tried to arrange $subject via create database icu encoding 'utf8' lc_ctype "en-US-x-icu" lc_collate "en-US-x-icu" template template0; and got only ERROR: invalid locale name: "en-US-x-icu" which is unsurprising after looking into the code, because createdb() checks those parameters with