Date: Wed, 20 Dec 2000 10:27:56 +0100
From: Michael Meskes <meskes@postgresql.org>
To: Brian Buhrow <buhrow@lothlorien.nfbcal.org>
Cc: Michael Meskes <meskes@postgresql.org>, pgsql-interfaces@postgresql.org
Subject: Re: Possible memory leak in Postgres V7.0.2/ecpg 2.7.1
Message-ID: <20001220102756.D17254@feivel.credativ.de>
Mail-Followup-To: Brian Buhrow <buhrow@lothlorien.nfbcal.org>,
	Michael Meskes <meskes@postgresql.org>,
	pgsql-interfaces@postgresql.org
References: <meskes@postgresql.org>
	<200012191814.KAA09195@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: <200012191814.KAA09195@lothlorien.nfbcal.org>;
	from buhrow@lothlorien.nfbcal.org on Tue, Dec 19, 2000 at
	10:14:36AM -0800

On Tue, Dec 19, 2000 at 10:14:36AM -0800, Brian Buhrow wrote:
> 	Thanks for the reply.  Yes, the allocations are requested
> just before the exec sql declare cursor statement.  

Now that is interesting, because the declare statement has no operation. It
gets executed at the open cursor statement. So only the preprocessor itself
can eat memory here.

> Yes, I've been using the example test sources  as examples on how to
> interface with ecpg, but the comments in those sources are not verbose.  Is
> there a good book which more fully describes the features of ecpg?

Unfortunately there is not enough documentation available.

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