Re: plperl doesn't release memory

From: Greg Stark <gsstark(at)mit(dot)edu>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: plperl doesn't release memory
Date: 2005-03-24 23:58:10
Message-ID: 877jjw4mwd.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Dan Sugalski <dan(at)sidhe(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-03-25 00:16:18 Re: plperl doesn't release memory
Previous Message Kris Jurka 2005-03-24 23:44:05 Re: [JDBC] plpgsql function with RETURNS SETOF refcursor AS. How