From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: _SPI_execute_plan failed to return result tuple table to caller |
Date: | 2005-10-01 18:43:20 |
Message-ID: | 20051001184320.3C011D942C@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
_SPI_execute_plan failed to return result tuple table to caller in
the ProcessUtility case, resulting in an intratransaction memory leak
if a utility command actually did return any tuples, as reported by
Dmitry Karasik. Fix this and also make the behavior more consistent
for cases involving nested SPI operations and multiple query trees,
by ensuring that we store the state locally until it is ready to be
returned to the caller.
Modified Files:
--------------
pgsql/src/backend/executor:
spi.c (r1.141 -> r1.142)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/spi.c.diff?r1=1.141&r2=1.142)
pgsql/src/include/executor:
spi_priv.h (r1.22 -> r1.23)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/executor/spi_priv.h.diff?r1=1.22&r2=1.23)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-10-02 23:50:16 | pgsql: Change nextval and other sequence functions to specify their |
Previous Message | Bruce Momjian | 2005-10-01 01:42:44 | pgsql: Adjust wording. |