Skip site navigation (1) Skip section navigation (2)

pgsql: Fix multiple memory leaks in PLy_spi_execute_fetch_result: it

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix multiple memory leaks in PLy_spi_execute_fetch_result: it
Date: 2010-04-30 19:15:51
Message-ID: 20100430191551.2373B7541D2@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Fix multiple memory leaks in PLy_spi_execute_fetch_result: it would leak
memory if the result had zero rows, and also if there was any sort of error
while converting the result tuples into Python data.  Reported and partially
fixed by Andres Freund.

Back-patch to all supported versions.  Note: I haven't tested the 7.4 fix.
7.4's configure check for python is so obsolete it doesn't work on my
current machines :-(.  The logic change is pretty straightforward though.

Tags:
----
REL8_4_STABLE

Modified Files:
--------------
    pgsql/src/pl/plpython:
        plpython.c (r1.122.2.2 -> r1.122.2.3)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/plpython.c?r1=1.122.2.2&r2=1.122.2.3)

pgsql-committers by date

Next:From: Tom LaneDate: 2010-04-30 19:15:58
Subject: pgsql: Fix multiple memory leaks in PLy_spi_execute_fetch_result: it
Previous:From: Tom LaneDate: 2010-04-30 19:15:45
Subject: pgsql: Fix multiple memory leaks in PLy_spi_execute_fetch_result: it

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group