Postgres Pro
Downloads
Home   >   mailing lists

Re: Is there a memory leak in commit 8561e48? - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Is there a memory leak in commit 8561e48?
Date
Msg-id 20180504133755.GD1592@paquier.xyz
Whole thread Raw
In response to Re: Is there a memory leak in commit 8561e48?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Tree view 
On Thu, May 03, 2018 at 08:45:13AM -0400, Peter Eisentraut wrote:
> I went with the patch I had posted, since I needed to move ahead with
> something.  If it turns out to be a problem, we can easily switch it
> around.

Okay.

> As Tom mentioned, in order to grow the SPI stack to where it has a
> significant size, you might also overrun the OS stack and other things.
> On the other hand, the current/new arrangement is a win for normal SPI
> use, since you don't need to rebuild the stack on every call.

It would be nice to mention that in the release notes..
--
Michael
Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pg_dump should use current_database() instead of PQdb()
Next
From: Michael Paquier
Date:
Subject: Re: Moving libpg{common,port,feutils}.a to pkglibdir?