| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | db(at)zigo(dot)dhs(dot)org, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: UTF8MatchText |
| Date: | 2007-05-21 13:43:47 |
| Message-ID: | 10140.1179755027@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> But why are we doing that CHAREQ?
To avoid the cost of the recursive call, just like it says.
> If it succeeds we'll
> just do it again when we recurse, I think.
If you move the other two cases then you could advance t and p before
entering the recursion.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Csaba Nagy | 2007-05-21 13:53:29 | Re: Re: [Oledb-dev] double precision error with pg linux server, but not with windows pg server |
| Previous Message | Andrew Dunstan | 2007-05-21 13:34:23 | Re: UTF8MatchText |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2007-05-21 14:03:02 | Re: Synchronized Scan |
| Previous Message | Andrew Dunstan | 2007-05-21 13:34:23 | Re: UTF8MatchText |