| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | ishii(at)sraoss(dot)co(dot)jp, tgl(at)sss(dot)pgh(dot)pa(dot)us, andres(at)anarazel(dot)de, pgsql-hackers(at)postgresql(dot)org, teodor(at)sigaev(dot)ru |
| Subject: | Re: pg_trgm |
| Date: | 2010-05-28 06:21:09 |
| Message-ID: | 1275027669.12486.1.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On fre, 2010-05-28 at 10:04 +0900, Tatsuo Ishii wrote:
> > I think the problem at hand has nothing at all to do with agglutination
> > or CJK-specific issues. You will get the same problem with other
> > languages *if* you set a locale that does not adequately support the
> > characters in use. E.g., Russian with locale C and encoding UTF8:
> >
> > select similarity(E'\u0441\u043B\u043E\u043D', E'\u0441\u043B\u043E
> > \u043D\u044B');
> > similarity
> > ────────────
> > NaN
> > (1 row)
>
> Wait. This works fine for me with stock pg_trgm. local is C and
> encoding is UTF8. What version of PostgreSQL are you using? Mine is
> 8.4.4.
This is in 9.0, because 8.4 doesn't recognize the \u escape syntax. If
you run this in 8.4, you're just comparing a sequence of ASCII letters
and digits.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2010-05-28 06:26:07 | Patch submission deadline for CommitFest 2010-07 |
| Previous Message | Sander, Ingo (NSN - DE/Munich) | 2010-05-28 04:26:27 | Re: Streaming Replication: Checkpoint_segment and wal_keep_segments on standby |