Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 90FFF475B8D for ; Fri, 27 Dec 2002 23:14:30 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id C46F3475461 for ; Fri, 27 Dec 2002 23:14:29 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id gBS4EXd0000168; Fri, 27 Dec 2002 23:14:33 -0500 (EST) To: ljb Cc: pgsql-interfaces@postgresql.org Subject: Re: still memory leaks with libpgtcl In-reply-to: References: Comments: In-reply-to ljb message dated "Sat, 28 Dec 2002 02:59:01 +0000" Date: Fri, 27 Dec 2002 23:14:33 -0500 Message-ID: <167.1041048873@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200212/73 X-Sequence-Number: 3486 ljb 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