| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Ian Harding <ianh(at)tpchd(dot)org>, <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [GENERAL] Memory Errors... |
| Date: | 2002-09-20 16:39:26 |
| Message-ID: | Pine.LNX.4.44.0209201838200.1307-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamar Owen | 2002-09-20 16:40:45 | Novell releasing PostgreSQL for NetWare. |
| Previous Message | Shridhar Daithankar | 2002-09-20 16:30:43 | Re: Improving speed of copy |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Copeland | 2002-09-20 17:57:34 | Re: [GENERAL] Memory Errors... |
| Previous Message | Tom Lane | 2002-09-20 13:57:59 | Re: DROP COLUMN misbehaviour with multiple inheritance |