From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | <pgman(at)candle(dot)pha(dot)pa(dot)us>, <phede-ml(at)islande(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Unicode combining characters |
Date: | 2001-10-03 15:23:47 |
Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA41EB3A6@m0114.s-mxs.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> > ... There seems some problems existing in the
> > implementation. Considering REGEX is not so slow, maybe we should
> > employ the same design as REGEX. i.e. using wide charcters, not
> > multibyte streams...
>
> Seems like a good thing to put on the to-do list. In the meantime,
> we still have the question of whether to enable multibyte in the
> default configuration. I'd still vote YES, as these results seem
> to me to demonstrate that there is no wide-ranging performance
penalty.
> A problem confined to LIKE on long strings isn't a showstopper IMHO.
As I said, with a valid not anchored like expression the performance
difference was substantial, even for shorter strings it was 37%.
The test with "like 'aaa'" was not a good test case, and we should not
deduce anything from that.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-10-03 16:05:34 | Re: Unicode combining characters |
Previous Message | Tom Lane | 2001-10-03 14:56:04 | Re: Unicode combining characters |