Skip site navigation (1) Skip section navigation (2)

Re: UTF8MatchText

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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

In response to

Responses

pgsql-hackers by date

Next:From: Csaba NagyDate: 2007-05-21 13:53:29
Subject: Re: Re: [Oledb-dev] double precision error with pg linuxserver, but not with windows pg server
Previous:From: Andrew DunstanDate: 2007-05-21 13:34:23
Subject: Re: UTF8MatchText

pgsql-patches by date

Next:From: Peter EisentrautDate: 2007-05-21 14:03:02
Subject: Re: Synchronized Scan
Previous:From: Andrew DunstanDate: 2007-05-21 13:34:23
Subject: Re: UTF8MatchText

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group