Re: Leaking regexp_replace in 9.3.1 ? (was: [HACKERSUninterruptable regexp_replace in 9.3.1 ?)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sandro Santilli <strk(at)keybit(dot)net>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, Florian Pflug <fgp(at)phlo(dot)org>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Leaking regexp_replace in 9.3.1 ? (was: [HACKERSUninterruptable regexp_replace in 9.3.1 ?)
Date: 2014-03-18 23:41:32
Message-ID: 32100.1395186092@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Sandro Santilli <strk(at)keybit(dot)net> writes:
> Tom: I saw you pushed a fix for the interruptability with this:
> https://github.com/postgres/postgres/commit/f5f21315d25ffcbfe7c6a3fa6ffaad54d31bcde0

> But we also noticed a memory leak in the regepx_replace call, did you notice
> that in your tests ? Same regexp as reported. Do you need another testcase ?

I see no memory growth while running your original example against HEAD.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Sergey Konoplev 2014-03-19 00:29:05 Re: BUG #9135: PostgreSQL doesn't want use index scan instead of (index scan+sort+limit)
Previous Message Andres Freund 2014-03-18 17:55:09 Re: BUG #9118: WAL Sender does not disconnect replication clients during shutdown

Browse pgsql-hackers by date

  From Date Subject
Next Message Maxence Ahlouche 2014-03-18 23:45:10 GSoC application: MADlib k-medoids clustering
Previous Message Tatsuo Ishii 2014-03-18 23:27:43 logical decoding doc