Gerhard Hintermayer wrote:
> Weird, I thought these were fixed already.
> Downloaded 7.2.3 source today, was *a lot* astonished, that the
> pg_on_connection_loss and the fix for finding a free connection slot
> (PSetResultId) were not in the source tarball.
> Fetched latest versions from CVS (both patches included), compiled tcl
> 8.3.5 and did
> set conn [pg_connect template1]
> pg_disconnect $conn
> in an endless loop, which result's in a constant increase in memory usage.
> Has anybody encountered this problem also ?
> What went wrong here - the sources in the tarball are oviously old (I
> submitted 2 patches several month ago, one was a bug fix, ok the other
> was an enhancement, but can anybody explain, why at least the bug fix
> did *not* find it's way to the tarball , and why are there 2 projects in
> parallel - libpgtcl and the pgtcl project - that is only confusing people.
> Has anyone experience with pgtcl project, it is still beta, and I'm in a
> production environment, so I need really stable stuff.
Is there absoulutely noone using postgreSQL with tcl/tk ? I cannot beleave that.
I'd be happy to hear at least the preferred pgtcl sources -either from the
postgreSQL sources of from the pgtcl project. And what's the differences ?
In response to
pgsql-interfaces by date
|Next:||From: ljb||Date: 2002-12-28 02:59:01|
|Subject: Re: still memory leaks with libpgtcl|
|Previous:||From: Tom Lane||Date: 2002-12-26 18:07:16|
|Subject: Re: [BUGS] pgdb.py is still wrong [not just] in Postgres 7.3.1 rpm |