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 E1SSMTJ-0002Wc-F2@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_1_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/05a86891232e1bd5e43d559f30bec2fc00131f37

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