From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "P(dot)N(dot)Guru Prasad" <pnguruji(at)yahoo(dot)com>, pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Memory leak!! |
Date: | 2003-04-12 15:10:42 |
Message-ID: | 87ptnriwel.fsf@stark.dyndns.tv |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> "P.N.Guru Prasad" <pnguruji(at)yahoo(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | ms | 2003-04-12 16:50:28 | does psqlodbc support UpdateBatch ? (ADO VB6) |
Previous Message | Tom Lane | 2003-04-12 05:26:26 | Re: Speed of SSL connections; cost of renegotiation |