Re: [GENERAL] Memory Errors...
От | Greg Copeland |
---|---|
Тема | Re: [GENERAL] Memory Errors... |
Дата | |
Msg-id | 1032544655.3107.87.camel@mouse.copelandconsulting.net обсуждение исходный текст |
Ответ на | Re: [GENERAL] Memory Errors... (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: [GENERAL] Memory Errors...
|
Список | pgsql-hackers |
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. > > -- > Peter Eisentraut peter_e@gmx.net > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster
В списке pgsql-hackers по дате отправления: