| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | emre(at)hasegeli(dot)com, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Wrong Results from SP-GiST with Collations |
| Date: | 2018-04-10 16:38:12 |
| Message-ID: | CAH2-Wz=fBmXr5M=b8oQgD_k+V8jXAXOq1Zho_jz9kmUkPF86dw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg토토 캔SQL : Postg토토 캔SQL 메일 링리스트 : 2018-04-10 이후 PGSQL-BUGS 16:38 |
On Tue, Apr 10, 2018 at 9:21 AM, Emre Hasegeli <emre(at)hasegeli(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2018-04-10 19:55:50 | Re: BUG #15144: *** glibc detected *** postgres: postgres smsconsole [local] SELECT: double free or corruption (!pre |
| Previous Message | Emre Hasegeli | 2018-04-10 16:21:58 | Wrong Results from SP-GiST with Collations |