What do you see as an appropriate resolution to this problem?

Do you have any additional insight on this? Shouldn't this be fixed by
InterBase and what does Firebird do in this case?

Jason Wharton

> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of Ulf Grasse
> Sent: Friday, October 28, 2005 3:40 PM
> To: IBObjects@yahoogroups.com
> Subject: Re: [IBO] Orphaned Statements
>
>
> While that is correct, the problem is that IB's memory management
> seems overwhelmed by this. Some compile statements take up as much as
> 15MB (that's Megabytes), and once you get to a point of having
> hundreds of orphaned statements, it poses a severe performance
> problem.
>
> It's plausible to think that IB ought to reuse prepared statement in
> the context of a new transaction, but that doesn't seem to be the case
> -- memory simply grows, and statements remain "STALLED" and orphaned.
> And we have word from IB that this happens only when a statement
> handle is not released prior to releasing the transaction.
>