Re: Memory leak!! - Mailing list pgsql-interfaces

From Greg Stark
Subject Re: Memory leak!!
Date
Msg-id 87ptnriwel.fsf@stark.dyndns.tv
Whole thread Raw
In response to Re: Memory leak!!  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-interfaces
Tom Lane <tgl@sss.pgh.pa.us> writes:

> "P.N.Guru Prasad" <pnguruji@yahoo.com> writes:
> > while (1) {
> >   print "sql executed and returned :", $Dbh->prepare("select user_id from
> > users limit 1")->execute, "\n"; 
> > }
> 
> I'm not a DBI user, but I'd kinda expect that executing a query would
> result in an object holding the results from that query.  Don't you need
> to do something to close/delete the result objects you're generating?

Perl reference counts these objects so that shouldn't be a problem.

You could be sure by using Devel::LeakTrace or Devel::Leak or something like
that. But I suspect they won't find anything because I suspect the problem is
in the DBD::pg driver or libpq at the C level.

--
greg



pgsql-interfaces by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Speed of SSL connections; cost of renegotiation
Next
From: Stéphane Pinel
Date:
Subject: libpq.dll