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 E1SSMTd-0002X0-SK@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
------
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(-)


pgsql-committers by date:

Previous
From: Joe Conway
Date:
Subject: pgsql: PL/pgSQL RETURN NEXT was leaking converted tuples, causing
Next
From: Joe Conway
Date:
Subject: pgsql: PL/pgSQL RETURN NEXT was leaking converted tuples, causing