From: Tom Lane <tgl@sss.pgh.pa.us>
To: ljb <lbayuk@mindspring.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: still memory leaks with libpgtcl
Date: Fri, 27 Dec 2002 23:14:33 -0500
Message-ID: <167.1041048873@sss.pgh.pa.us> (raw)
In-Reply-To: <auj41k$f4v$1@news.hub.org>
References: <as0da6$2njk$1@news.hub.org>
<auhq8v$2iuo$1@news.hub.org>
<auj41k$f4v$1@news.hub.org>
ljb <lbayuk@mindspring.com> writes:
> 3) Memory leak on connect/disconnect unfortunately is not fixed in either
> the production or beta versions. I'm seeing about 4KB loss per
> connect/disconnect.
The notes I made about this say:
2002-09-02 19:41 tgl
* src/interfaces/libpgtcl/: pgtclCmds.c, pgtclId.c: Partial
solution for 'unexpected EOF' problem with pg_disconnect: it seems
we have a choice between annoying messages and leaking memory (or
dumping core, but that's right out).
That was nearly four months ago, and so I don't recall the details,
other than that I went for the "leak memory" choice :-(
If anyone can improve the situation, step right up with a patch ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, lbayuk@mindspring.com
Subject: Re: still memory leaks with libpgtcl
In-Reply-To: <167.1041048873@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox