Re: Pathological regexp match - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Pathological regexp match
Date
Msg-id 9837222c1001290514q3978889as3bba94b84714f69b@mail.gmail.com
Whole thread Raw
In response to Re: Pathological regexp match  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Pathological regexp match  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
2010/1/29 Alvaro Herrera <alvherre@commandprompt.com>:
> Hi Michael,
>
> Michael Glaesemann wrote:
>> We came across a regexp that takes very much longer than expected.
>>
>> PostgreSQL 8.4.1 on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44), 64-bit
>>
>> SELECT 'ooo...' ~ $r$Z(Q)[^Q]*A.*?(\1)$r$; -- omitted for email brevity
>
> The ? after .* is pointless.  If you remove it, the query returns
> immediately.
>
> (There's a badly needed CHECK_FOR_INTERRUPTS in this code BTW)

Incidentally, I ran across the exact same issue with a non-greedy
regexp with a client earlier this week, and put on my TODO to figure
out a good place to stick a check for interrupts. Does this mean I
don't have to, because you're on it? ;)


-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Hot Standby: Relation-specific deferred conflict resolution
Next
From: Magnus Hagander
Date:
Subject: Re: WARNING: pgstat wait timeout