| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | peter_e(at)gmx(dot)net |
| Cc: | ishii(at)postgresql(dot)org, 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-30 14:52:37 |
| Message-ID: | 20100530.235237.02328287.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > > 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.
I just wanted to point out from the point of view of users. I do not
object the new \u escape syntax. I think pg_trgm has a problem. But
Tom thinks that it's not a problem. That's the point.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2010-05-30 16:29:31 | Re: Re: [RFC][PATCH]: CRC32 is limiting at COPY/CTAS/INSERT ... SELECT + speeding it up |
| Previous Message | Tom Lane | 2010-05-30 14:50:19 | Re: functional call named notation clashes with SQL feature |