From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | phede-ml(at)islande(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Unicode combining characters |
Date: | 2001-10-02 16:31:40 |
Message-ID: | 200110021631.f92GVeY12814@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
If no one can find a case where multibyte is slower, I think we should
enable it by default. Comments?
> > Also, have we decided if multibyte should be the configure default now?
>
> Not sure.
>
> Anyway I have tested LIKE/REGEX query test using current. The query
> executed is:
>
> explain analyze select '0000000 5089 474e...( 16475
> bytes long text containing only 0-9a-z chars) like 'aaa';
>
> and
>
> explain analyze select '0000000 5089 474e...( 16475
> bytes long text containing only 0-9a-z chars) ~ 'aaa';
>
> Here is the result:
>
> no MB with MB
> LIKE 0.09 msec 0.08 msec
> REGEX 0.09 msec 0.10 msec
>
> LIKE with MB seemed to be resonably fast, but REGEX with MB seemed a
> little bit slow. Probably this is due the wide character conversion
> overhead.
> --
> Tatsuo Ishii
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 2001-10-02 16:35:45 | Re: cvs problem |
Previous Message | Bruce Momjian | 2001-10-02 16:29:08 | Re: do we're in time to catch 7.2 Beta ? |