Skip site navigation (1) Skip section navigation (2)

Re: Possible memory leak in Postgres V7.0.2/ecpg 2.7.1

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Brian Buhrow <buhrow(at)lothlorien(dot)nfbcal(dot)org>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Possible memory leak in Postgres V7.0.2/ecpg 2.7.1
Date: 2000-12-20 09:27:56
Message-ID: 20001220102756.D17254@feivel.credativ.de (view raw or flat)
Thread:
Lists: pgsql-interfaces
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(at)Fam-Meskes(dot)De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!

In response to

pgsql-interfaces by date

Next:From: D'Arcy J.M. CainDate: 2000-12-20 10:08:19
Subject: Re: Python and PSQL
Previous:From: Karel ZakDate: 2000-12-20 07:56:43
Subject: PL/Python (was: Re: [GENERAL] Re: [HACKERS] Trigger)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group