Re: [Sqlgrey-users] Solution to sqlgrey & postgresql memory leaks?

[Lionel B. <lio...@bo...>]

Adam Sjøgren wrote the following on 11.08.2007 12:56 :
> On Mon, 06 Aug 2007 16:48:04 +0200, Lionel wrote:
>
>   
>> So this leak seemed to be in the InactiveDestroy handling of recent DBI
>> or DBD-*.
>>     
>
> There was recently a nice description of how to handle $dbh, forking and
> InactiveDestroy over on the DBD::Pg mailinglist:
>
>  <http://article.gmane.org/gmane.comp.db.postgresql.dbdpg/2276>
>
>   

I suspect that the problem with asynchronous cleanup is linked to the
fact that I reuse the same variable in the forked process to store the
new database handle. To avoid the handle to be closed I set it up to
InactiveDestroy, but it seems the name of this hash key does not reflect
its real purpose. If I remember correctly I thought that the logic was
actually the opposite of the one described in the perldoc
(InaciveDestroy on the father instead of the child) because it was the
only setup that sometimes worked.
It seems you simply can't reuse the same variable in the children.
Odd... I'll have a look at that in the future to resurrect the
asynchronous cleanup.

Lionel