To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "P.N.Guru Prasad" <pnguruji@yahoo.com>,
	pgsql-interfaces@postgresql.org
Subject: Re: Memory leak!!
References: <Pine.LNX.4.44.0304081322260.1571-100000@MainServer.bksys.co.in>
	<4468.1049864296@sss.pgh.pa.us>
In-Reply-To: <4468.1049864296@sss.pgh.pa.us>
From: Greg Stark <gsstark@mit.edu>
Organization: The Emacs Conspiracy; member since 1992
Date: 12 Apr 2003 11:10:42 -0400
Message-ID: <87ptnriwel.fsf@stark.dyndns.tv>
Lines: 20
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

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