| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | 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 04:14:47 |
| Message-ID: | 22577.1002082487@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
>> I'd feel more confident if the measurements were done using operators
>> repeated enough times to yield multiple-second runtimes.
> Any idea to do that?
Maybe something like this: declare a plpgsql function that takes two
text parameters and has a body like
for (i = 0 to a million)
boolvar := $1 like $2;
Then call it with strings of different lengths and see how the runtime
varies. You need to apply the LIKE to function parameters, else the
system will probably collapse the LIKE operation to a constant...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2001-10-03 05:41:34 | timestamp and time now support precision |
| Previous Message | Dave Harkness | 2001-10-03 02:37:40 | PROBLEM SOLVED: LOCK TABLE oddness in PLpgSQL function called via JDBC |