On 20 Sep 2002, Greg Copeland wrote: > I'll try to have a look-see by the end of the weekend. Any code that > can reproduce it or is it ANY code that uses SPI? > > Greg > > > On Fri, 2002-09-20 at 11:39, Peter Eisentraut wrote: > > 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.
I've added the call to free the tuptable just as in the pltcl patch I submited earlier (which I can't remember if I've seen in the list so I may well resend). However, the comments in the code imply there might be another leak with prepared plans. I'm looking into that so I won't be sending this patch just yet. -- Nigel J. Andrews ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
