pgsql: PL/pgSQL RETURN NEXT was leaking converted tuples, causing - Mailing list pgsql-committers

From Joe Conway
Subject pgsql: PL/pgSQL RETURN NEXT was leaking converted tuples, causing
Date
Msg-id E1SSMT4-0002WG-PE@gemulon.postgresql.org
Whole thread Raw
List 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(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Improve tests for postmaster death in auxiliary processes.
Next
From: Joe Conway
Date:
Subject: pgsql: PL/pgSQL RETURN NEXT was leaking converted tuples, causing