| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Cc: | ZeugswetterA(at)spardat(dot)at, 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-04 03:05:16 |
| Message-ID: | 15665.1002164716@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> To accomplish this, I moved MatchText etc. to a separate file and now
> like.c includes it *twice* (similar technique used in regexec()). This
> makes like.o a little bit larger, but I believe this is worth for the
> optimization.
That sounds great.
What's your feeling now about the original question: whether to enable
multibyte by default now, or not? I'm still thinking that Peter's
counsel is the wisest: plan to do it in 7.3, not today. But this fix
seems to eliminate the only hard reason we have not to do it today ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lincoln Yeoh | 2001-10-04 03:15:52 | Feature suggestion: Postgresql binding to one IP? |
| Previous Message | Tom Lane | 2001-10-04 02:47:28 | Re: BUG: text(varchar) truncates at 31 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2001-10-04 03:43:23 | Re: Unicode combining characters |
| Previous Message | Tatsuo Ishii | 2001-10-04 02:16:42 | Re: Unicode combining characters |