| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: UTF8MatchText |
| Date: | 2007-05-17 19:48:47 |
| Message-ID: | 12299.1179431327@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> Except that the entire point of this patch is to dumb down NextChar to
>> be the same as NextByte for UTF8 strings.
> That's not what I see in (what I think is) the latest submission, which
> includes this snippet:
[ scratches head... ] OK, then I think I totally missed what this patch
is trying to accomplish; because this code looks just the same as the
existing multibyte-character operations. Where does the performance
improvement come from?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2007-05-17 19:49:24 | Re: 8.3 release date on web site |
| Previous Message | Tom Lane | 2007-05-17 19:35:08 | pgsql: Fix parameter recalculation for Limit nodes: during a ReScan call |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-05-17 19:57:25 | Re: UTF8MatchText |
| Previous Message | Tom Lane | 2007-05-17 19:42:28 | Re: updated SORT/LIMIT patch |