Re: Explicit deterministic COLLATE fails with pattern matching operations on column with non-deterministic collation

From: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "James Lucas" <jlucasdba(at)gmail(dot)com>,"David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>,"PostgreSQL mailing lists" <pgsql-bugs(at)lists(dot)postgresql(dot)org>,"Peter Eisentraut" <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: Explicit deterministic COLLATE fails with pattern matching operations on column with non-deterministic collation
Date: 2020-05-28 18:48:38
Message-ID: 6351fb21-8282-406c-af64-22a3c9e1219b@manitou-mail.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane wrote:

> I suspect that the 'en-US-ks-level2' ICU locale doesn't act as you
> think it does.

Indeed, because the syntax is tricky. The OP wants 'en-US-u-ks-level2'.
With 'en-US-ks-level2', the ks-level2 component is ignored and you
get a tertiary colstrength.

Or use 'en-US(at)colStrength=secondary' which is possibly more
readable and works with older versions of ICU.

Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message James Lucas 2020-05-28 20:42:07 Re: Explicit deterministic COLLATE fails with pattern matching operations on column with non-deterministic collation
Previous Message Tom Lane 2020-05-28 18:29:28 Re: Explicit deterministic COLLATE fails with pattern matching operations on column with non-deterministic collation