From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | t-ishii(at)sra(dot)co(dot)jp |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Constantin Teodorescu <teo(at)flex(dot)ro>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Broken select on regular expression !!! |
Date: | 1999-05-21 15:46:05 |
Message-ID: | 199905211546.LAA23931@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Ole Gjerde | 1999-05-21 16:36:55 | Re: [HACKERS] Current TODO list |
Previous Message | Tom Lane | 1999-05-21 15:07:02 | Re: [HACKERS] Empty system tables |