From: | Sandro Santilli <strk(at)keybit(dot)net> |
---|---|
To: | Pedro Gimeno <pgsql-004(at)personal(dot)formauri(dot)es> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: uninterruptable regexp_replace in 9.2 and 9.3 |
Date: | 2014-03-03 08:31:09 |
Message-ID: | 20140303083109.GA6588@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sun, Mar 02, 2014 at 02:07:29PM +0100, Pedro Gimeno wrote:
> Tom Lane wrote, On 2014-03-02 05:38:
>
> > The performance problem we're looking at comes directly from the
> > backtracking that's done to ensure that we detect a match in case the
> > pattern has this sort of pathological behavior.
>
> It is my understanding that the bug reported by the OP is not a
> performance problem, but PostgreSQL's failure to interrupt the
> processing if it takes too long, when statement_timeout is set.
Yes, this is my main concern.
Of course it'd be nice to get a faster response, even if ill, but
as long as statement_timeout is effective I'm happy.
--strk;
() ASCII ribbon campaign -- Keep it simple !
/\ http://strk.keybit.net/rants/ascii_mails.txt
From | Date | Subject | |
---|---|---|---|
Next Message | proels | 2014-03-03 12:53:42 | BUG #9420: WAL-Sender repeatedly killed |
Previous Message | pboake | 2014-03-03 03:24:42 | BUG #9416: Setting up postgresql-9.1 (9.1.12-0wheezy1) Fails Configuration |