| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | t-ishii(at)sra(dot)co(dot)jp, 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 06:19:20 |
| Message-ID: | 199905210619.PAA12109@srapc451.sra.co.jp |
| 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.
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 1999-05-21 09:58:18 | ERROR: WaitOnLock: error on wakeup - Aborting this transaction |
| Previous Message | Bruce Momjian | 1999-05-21 05:53:39 | Re: [HACKERS] Broken select on regular expression !!! |