From: | Dan Sugalski <dan(at)sidhe(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Sven Willenberger <sven(at)dmv(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: plperl doesn't release memory |
Date: | 2005-03-24 20:36:46 |
Message-ID: | a06210207be68d4cd49bc@[192.168.0.8] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
At 3:14 PM -0500 3/24/05, Tom Lane wrote:
>Dan Sugalski <dan(at)sidhe(dot)org> writes:
>> ... I'm pretty sure for embedding use it uses whatever routines
>> the embedder defines, but it's been a while since I've poked around
>> in there.
>
>Hmm. plperl is definitely not doing anything to try to manipulate that
>behavior; maybe it should? Where can we find out about this?
I'll have to go dig, but this:
> > Anyway, if perl's using its own memory allocator you'll want to
>> rebuild it to not do that.
>
>When I tried to test this it seemed that memory did get released at the
>conclusion of each query --- at least "top" showed the backend process
>size dropping back down. But, again, I wouldn't be surprised if Sven's
>perl installation is configured differently than mine.
...implies perl's doing the Right Thing, otherwise there'd be no
release of memory to the system.
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
dan(at)sidhe(dot)org have teddy bears and even
teddy bears get drunk
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-03-24 20:52:55 | Re: plperl doesn't release memory |
Previous Message | Sven Willenberger | 2005-03-24 20:26:00 | Re: plperl doesn't release memory |