Re: plperl doesn't release memory - Mailing list pgsql-general

From Greg Stark
Subject Re: plperl doesn't release memory
Date
Msg-id 877jjw4mwd.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: plperl doesn't release memory  (Dan Sugalski <dan@sidhe.org>)
Responses Re: plperl doesn't release memory  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: plperl doesn't release memory  (Dan Sugalski <dan@sidhe.org>)
List pgsql-general
Dan Sugalski <dan@sidhe.org> writes:

> Anyway, if perl's using its own memory allocator you'll want to rebuild it
> to not do that.

You would need to do that if you wanted to use a debugging malloc. But there's
no particular reason to think that you should need to do this just to work
properly.

Two mallocs can work fine alongside each other. They each call mmap or sbrk to
allocate new pages and they each manage the pages they've received. They won't
have any idea why the allocator seems to be skipping pages, but they should be
careful not to touch those pages.

--
greg

pgsql-general by date:

Previous
From: Kris Jurka
Date:
Subject: Re: [JDBC] plpgsql function with RETURNS SETOF refcursor AS. How
Next
From: Tom Lane
Date:
Subject: Re: plperl doesn't release memory