Re: 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: Greg Stark <stark(at)mit(dot)edu>
Cc: Sandro Santilli <strk(at)keybit(dot)net>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Florian Pflug <fgp(at)phlo(dot)org>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Re: Leaking regexp_replace in 9.3.1 ? (was: [HACKERSUninterruptable regexp_replace in 9.3.1 ?)
Date: 2014-03-19 14:55:51
Message-ID: 30516.1395240951@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Greg Stark <stark(at)mit(dot)edu> writes:
> It looks like a simple bug pg_regexec where it's reusing a loop
> counter "n" to mean two different things. When it goes to free all the
> subdfas it looks like the code was written based "n" still being the
> number of trees but in fact it's been reused to be the number of
> matches.

Looks like it's my bug (how embarrassing). Thanks!

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message jkoceniak 2014-03-19 17:13:56 BUG #9635: Wal sender process is using 100% CPU
Previous Message Sandro Santilli 2014-03-19 12:11:02 Re: Leaking regexp_replace in 9.3.1 ? (was: [HACKERSUninterruptable regexp_replace in 9.3.1 ?)

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2014-03-19 15:34:08 four minor proposals for 9.5
Previous Message Robert Haas 2014-03-19 14:27:01 Re: logical decoding doc