Date: Tue, 19 Dec 2000 17:31:16 +0100
From: Michael Meskes <meskes@postgresql.org>
To: Brian Buhrow <buhrow@lothlorien.nfbcal.org>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Possible memory leak in Postgres V7.0.2/ecpg 2.7.1
Message-ID: <20001219173116.A10455@feivel.credativ.de>
Mail-Followup-To: Brian Buhrow <buhrow@lothlorien.nfbcal.org>,
	pgsql-interfaces@postgresql.org
References: <200012181821.KAA27945@lothlorien.nfbcal.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200012181821.KAA27945@lothlorien.nfbcal.org>;
	from buhrow@lothlorien.nfbcal.org on Mon, Dec 18, 2000 at
	10:21:47AM -0800

On Mon, Dec 18, 2000 at 10:21:47AM -0800, Brian Buhrow wrote:
> V7.0.2, using ecpg V2.7.1, included with the package.  I find that running
> a batch client I wrote leaks memory to the extent that the client bombs out
> a quarter of the way through its job.  Thinking it was my code, I traced
> ...
> not particularly familiar with the innards of the ecpg code, I thought I
> would ask if anyone has seen this sort of problem before.  My sql code is

I'm not sure. I've got some reports that I couldn't reproduce though.

> not particularly complicated, but I am using cursors, and it seems that
> these allocations happen just before "declare cursor" is executed.  Can

Before it is executed or before the exec sql declare statement?

> anyone help shed light on what might be going on, and how I might fix it?
> I can provide traces if that would help, as well as any debugging
> statements, if someone can tell me how to turn them on.

Just look into the test examples in the source code if you have them. Or
else I can send them to you. But the log won't help you much I guess. 

Are you able to try ecpg 2.8.0 and libecpg 3.2.0? I can send you the source
if you like.

Michael
-- 
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!