Re: [HACKERS] Broken select on regular expression !!!
| От | Tatsuo Ishii |
|---|---|
| Тема | Re: [HACKERS] Broken select on regular expression !!! |
| Дата | |
| Msg-id | 199905210619.PAA12109@srapc451.sra.co.jp обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Broken select on regular expression !!! (Bruce Momjian <maillist@candle.pha.pa.us>) |
| Ответы |
Re: [HACKERS] Broken select on regular expression !!!
|
| Список | 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
В списке pgsql-hackers по дате отправления: