Re: [GENERAL] PG-10 + ICU and abbreviated keys

2017-11-13 Thread Andreas Joseph Krogh
På tirsdag 14. november 2017 kl. 00:44:11, skrev Peter Geoghegan >: On Mon, Nov 13, 2017 at 2:05 PM, Andreas Joseph Krogh wrote: > When sorting on text, we're usually doing so using an multi-column index, like for instance "CREATE INDEX

Re: [GENERAL] PG-10 + ICU and abbreviated keys

2017-11-13 Thread Peter Geoghegan
On Mon, Nov 13, 2017 at 2:05 PM, Andreas Joseph Krogh wrote: > When sorting on text, we're usually doing so using an multi-column index, > like for instance "CREATE INDEX xxx ON my_table (lower(name) ASC, created > ASC)". Will abbreviated keys help here? Yes, they'll help

Re: [GENERAL] PG-10 + ICU and abbreviated keys

2017-11-13 Thread Andreas Joseph Krogh
På mandag 13. november 2017 kl. 22:28:40, skrev Peter Geoghegan >: On Mon, Nov 13, 2017 at 12:48 PM, Andreas Joseph Krogh wrote: > Thanks. As the person that worked on abbreviated keys, I'd like to hear about how you get with this. How

Re: [GENERAL] PG-10 + ICU and abbreviated keys

2017-11-13 Thread Peter Geoghegan
On Mon, Nov 13, 2017 at 12:48 PM, Andreas Joseph Krogh wrote: > Thanks. As the person that worked on abbreviated keys, I'd like to hear about how you get with this. How much faster is it for you? I don't usually get to hear about this, because most users don't notice that

Re: [GENERAL] PG-10 + ICU and abbreviated keys

2017-11-13 Thread Andreas Joseph Krogh
På mandag 13. november 2017 kl. 21:46:08, skrev Peter Geoghegan >: On Mon, Nov 13, 2017 at 12:40 PM, Peter Geoghegan wrote: >> Do I have to explicitly specify collation when using ORDER by on that column for index and abbreviated keys to be

Re: [GENERAL] PG-10 + ICU and abbreviated keys

2017-11-13 Thread Andreas Joseph Krogh
På mandag 13. november 2017 kl. 21:40:47, skrev Peter Geoghegan >: On Mon, Nov 13, 2017 at 11:48 AM, Andreas Joseph Krogh wrote: > Ok, so I have to explicitly specify like this: > > create table test(id serial primary key, name varchar

Re: [GENERAL] PG-10 + ICU and abbreviated keys

2017-11-13 Thread Peter Geoghegan
On Mon, Nov 13, 2017 at 12:40 PM, Peter Geoghegan wrote: >> Do I have to explicitly specify collation when using ORDER by on that column >> for index and abbreviated keys to be used? > > Only if you didn't define the column with a per-column collation initially. BTW, if you

Re: [GENERAL] PG-10 + ICU and abbreviated keys

2017-11-13 Thread Peter Geoghegan
On Mon, Nov 13, 2017 at 11:48 AM, Andreas Joseph Krogh wrote: > Ok, so I have to explicitly specify like this: > > create table test(id serial primary key, name varchar collate "nb_NO" not > null); That doesn't look like an ICU locale. You may mean "nb-NO-x-icu". But

Re: [GENERAL] PG-10 + ICU and abbreviated keys

2017-11-13 Thread Andreas Joseph Krogh
På mandag 13. november 2017 kl. 19:07:53, skrev Peter Geoghegan >: On Mon, Nov 13, 2017 at 12:27 AM, Andreas Joseph Krogh wrote: > In PG-10, with ICU enabled, is abbreviated keys now enabled? Yes. ICU will use abbreviated keys on every

Re: [GENERAL] PG-10 + ICU and abbreviated keys

2017-11-13 Thread Peter Geoghegan
On Mon, Nov 13, 2017 at 12:27 AM, Andreas Joseph Krogh wrote: > In PG-10, with ICU enabled, is abbreviated keys now enabled? Yes. ICU will use abbreviated keys on every platform, including Windows. > If so, using locale=nb_NO.UTF-8, do I have to use a ICU-specific locale to

Re: [GENERAL] PG-10 + ICU and abbreviated keys

2017-11-13 Thread Adrien Nayrat
On 11/13/2017 09:27 AM, Andreas Joseph Krogh wrote: >   > In PG-10, with ICU enabled, is abbreviated keys now enabled? >   Hello, I think yes : src/backend/utils/adt/varlena.c 1876 /* 1877 * Unfortunately, it seems that abbreviation for non-C collations is 1878 * broken on many

[GENERAL] PG-10 + ICU and abbreviated keys

2017-11-13 Thread Andreas Joseph Krogh
Hi.   In PG-10, with ICU enabled, is abbreviated keys now enabled?   If so, using locale=nb_NO.UTF-8, do I have to use a ICU-specific locale to take advantage of abbreviated keys?   Thanks.   -- Andreas Joseph Krogh CTO / Partner - Visena AS Mobile: +47 909 56 963 andr...@visena.com