Re: Wrong Results from SP-GiST with Collations - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: Wrong Results from SP-GiST with Collations
Date
Msg-id CAH2-Wz=fBmXr5M=b8oQgD_k+V8jXAXOq1Zho_jz9kmUkPF86dw@mail.gmail.com
Whole thread Raw
In response to Wrong Results from SP-GiST with Collations  (Emre Hasegeli <emre@hasegeli.com>)
Responses Re: Wrong Results from SP-GiST with Collations
List pgsql-bugs
On Tue, Apr 10, 2018 at 9:21 AM, Emre Hasegeli <emre@hasegeli.com> wrote:
> I assume we don't have any option than removing support for comparison
> operators with collations just like btree.

I can't imagine how this could ever work, since a non C-collation
string cannot be atomized into tokens like that. Considering each
token successively during a comparison does not always produce the
same answer as a straight comparison against the original string
would.

I believe that there are cases that won't work with *any* glibc or ICU
collation, not just "cs_CZ".

-- 
Peter Geoghegan


pgsql-bugs by date:

Previous
From: Emre Hasegeli
Date:
Subject: Wrong Results from SP-GiST with Collations
Next
From: Peter Geoghegan
Date:
Subject: Re: BUG #15144: *** glibc detected *** postgres: postgres smsconsole[local] SELECT: double free or corruption (!pre