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 E1SSMTu-0002Xf-Vi@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
------
REL8_4_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/564b257e44397f9d77a928b22a02b76a4b1534ac

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: Heikki Linnakangas
Date:
Subject: pgsql: Fix outdated comment.