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:14
Message-ID: E1SSMT4-0002WG-PE@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
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/b58bacdacbb15948cf24c786ebbb92213a2fe013

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:03:29 pgsql: PL/pgSQL RETURN NEXT was leaking converted tuples, causing
Previous Message Tom Lane 2012-05-10 04:55:12 pgsql: Improve tests for postmaster death in auxiliary processes.