Re: pg_trgm
Peter Eisentraut <peter_e@gmx.net>
From: Peter Eisentraut <peter_e@gmx.net>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: ishii@sraoss.co.jp, tgl@sss.pgh.pa.us, andres@anarazel.de, pgsql-hackers@postgresql.org, teodor@sigaev.ru
Date: 2010-05-30T11:36:57Z
Lists: pgsql-hackers
On sön, 2010-05-30 at 11:05 +0900, Tatsuo Ishii wrote: > > > 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. > > Hum. Still I prefer 8.4's behavior since anything is better than > returning NaN. It seems 9.0 does not have any escape route for > multibyte+C locale users. I think you are confusing some things here. The \u escape syntax is for string literals in general. The behavior of pg_trgm is still the same in 8.4 and in 9.0. It's just easier in 9.0 to write out examples relevant to the current problem.