Re: ICU collation support is incomplete for replacing citext in 10.beta4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rusty Conover <Rusty(dot)Conover(at)twosigma(dot)com>
Cc: "'pgsql-bugs(at)postgresql(dot)org'" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: ICU collation support is incomplete for replacing citext in 10.beta4
Date: 2017-09-07 18:43:33
Message-ID: 29619.1504809813@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Rusty Conover <Rusty(dot)Conover(at)twosigma(dot)com> writes:
> The support for ICU provided collations in PostgreSQL 10.beta4 adds the ability to have case insensitive collations. Which is a great thing, because citext can be very slow!

Apparently you've not read the previous discussions about this.

> Before continuing efforts into resolving these collation challenges, I'd
> like to know if this is considered a bug, or simply out of scope of
> PostgreSQL 10?

It is not a bug, and it is very far out of scope for PG 10.

There's some interest in making this more flexible, but changing the
behavior of hashtext() at all is going to be a pretty hard sell (since
that will break existing hash indexes, which we just got done making into
a production-grade feature). Making it dependent on a selectable ICU
locale seems even more of a nonstarter. And even if we had that working,
as you note, there are other issues that'd need to be resolved. I see
this as something that might possibly get done several years down the
pike.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Wong, Yi Wen 2017-09-07 20:02:34 Re: Old row version in hot chain become visible after a freeze
Previous Message Rusty Conover 2017-09-07 18:05:11 ICU collation support is incomplete for replacing citext in 10.beta4