pgsql: PL/pgSQL RETURN NEXT was leaking converted tuples, causing

From: Joe Conway <mail(at)joeconway(dot)com>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: PL/pgSQL RETURN NEXT was leaking converted tuples, causing
Date: 2012-05-10 06:03:49
Message-ID: E1SSMTd-0002X0-SK@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

PL/pgSQL RETURN NEXT was leaking converted tuples, causing
out of memory when looping through large numbers of rows.
Flag the converted tuples to be freed. Complaint and patch
by Joe.

Branch
------
REL9_0_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/5a96a0a8cf8cea3c5737fec9d37a75f012302f60

Modified Files
--------------
src/pl/plpgsql/src/pl_exec.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Joe Conway 2012-05-10 06:04:06 pgsql: PL/pgSQL RETURN NEXT was leaking converted tuples, causing
Previous Message Joe Conway 2012-05-10 06:03:29 pgsql: PL/pgSQL RETURN NEXT was leaking converted tuples, causing