Re: [HACKERS] Broken select on regular expression !!! - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] Broken select on regular expression !!!
Date
Msg-id 199905211546.LAA23931@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] Broken select on regular expression !!!  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-hackers
> >> >Again very clear, and caused by the indexing of regex's, as you suggest.
> >> >I can easily look for '|' in the string, and skip the optimization.  Is
> >> >that the only special case I need to add?
> >> 
> >> What about '{' ?
> >
> >Does it understand {?  Man, what kind of regex library do we have?
> 
> I vaguely recall that we used to support only "basic" regex. At least
> I thought so. Now looking into the source, I found we have supported
> "extended" regex. FYI, our regex routines definitely supprt '{'. See
> backend/regex/re_format.7.
> 
> P.S.    I will commit a small regex test program under
> backend/regex for the testing purpose.  

I have just commited a fix to skip {} too.

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Empty system tables
Next
From: Ole Gjerde
Date:
Subject: Re: [HACKERS] Current TODO list