| From: | Andrew - Supernews <andrew+nonews(at)supernews(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: LIKE optimization in UTF-8 and locale-C |
| Date: | 2007-03-23 06:10:39 |
| Message-ID: | slrnf06rqv.7me.andrew+nonews@atlantis.supernews.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On 2007-03-23, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> wrote:
> Thanks, it all made sense to me. My proposal was completely wrong.
Actually, I think your proposal is fundamentally correct, merely incomplete.
Doing octet-based rather than character-based matching of strings is a
_design goal_ of UTF8. Treating UTF8 like any other multibyte charset and
converting everything to wide-chars is, in my opinion, always going to
result in suboptimal performance.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2007-03-23 07:50:36 | Re: CREATE INDEX and HOT - revised design |
| Previous Message | Andrew - Supernews | 2007-03-23 06:00:20 | Re: LIKE optimization in UTF-8 and locale-C |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-03-23 08:20:51 | Re: contrib/spi makefile inconsistency |
| Previous Message | Andrew - Supernews | 2007-03-23 06:00:20 | Re: LIKE optimization in UTF-8 and locale-C |