Tom Lane writes:
> On looking a little more closely, it's clear that pltcl_SPI_exec()
> should be, and is not, calling SPI_freetuptable() once it's done with
> the tuple table returned by SPI_exec(). This needs to be done in all
> the non-elog code paths after SPI_exec has returned SPI_OK_SELECT.
There's a note in the PL/Python documentation that it's leaking memory if
SPI plans are used. Maybe that's related and someone could take a look at
it.
--
Peter Eisentraut peter_e@gmx.net