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:45
Message-ID: 20100430191545.9E6F87541D2@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
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.

Modified Files:
--------------
pgsql/src/pl/plpython:
plpython.c (r1.141 -> r1.142)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/plpython.c?r1=1.141&r2=1.142)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-04-30 19:15:51 pgsql: Fix multiple memory leaks in PLy_spi_execute_fetch_result: it
Previous Message Heikki Linnakangas 2010-04-30 18:43:03 Re: WAL page magic number (was Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct)