Re: Is there a memory leak in commit 8561e48?

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Is there a memory leak in commit 8561e48?
Дата
Msg-id 22655.1525189335@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Is there a memory leak in commit 8561e48?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: Is there a memory leak in commit 8561e48?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> The memory leak can be fixed by adding a pfree().

That seems like an odd way to approach this.  Why not just remove the
reset of _SPI_stack and _SPI_stack_depth, so as to subtract code rather
than adding it --- that is, make it actually work like you mistakenly
thought it did?  If we're going to keep the stack in TopMemoryContext,
there's no need to thrash it on every transaction.

            regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: stats_ext test fails with -DCATCACHE_FORCE_RELEASE
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Patch missing from back branches