Re: Death by regexp_replace

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Benedikt Grundmann <bgrundmann(at)janestreet(dot)com>, PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Death by regexp_replace
Date: 2016-01-15 15:48:25
Message-ID: CACjxUsNhFSYT9kCzf7RYb9Cr0e=48J-kjHvrH0BD0xNGuRfR+g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

On Fri, Jan 15, 2016 at 9:33 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

>> *WARNING DO NOT DO THIS ON A PRODUCTION BOX*
>> select regexp_replace('VODI GR,VOD LN,VOD LN,VODN MM,VODPF US,VOD US,VZC
>> LN', '([^,]+)(,*\1)+', '\1');

> This responds to cancel just fine for me.

> (FWIW, I think you probably wanted ,+ not ,* in the regex, else there's
> practically no constraint there, leading to having to consider O(N^2)
> or more possibilities.)

On master (commit cf7dfbf2) it responds to pg_cancel_backend(),
but it seems to be in an endless loop until you do that.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2016-01-15 16:05:33 Re: Truncating/vacuuming relations on full tablespaces
Previous Message Tom Lane 2016-01-15 15:33:52 Re: Death by regexp_replace

Browse pgsql-www by date

  From Date Subject
Next Message Benedikt Grundmann 2016-01-15 16:19:10 Re: Death by regexp_replace
Previous Message Tom Lane 2016-01-15 15:33:52 Re: Death by regexp_replace