X-Original-To: pgsql-interfaces@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 565C74793A0 for ; Fri, 31 Jan 2003 21:00:10 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 4713E47DF97 for ; Fri, 31 Jan 2003 19:08:57 -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 h1108p5u001580; Fri, 31 Jan 2003 19:08:52 -0500 (EST) To: Gerhard Hintermayer Cc: pgsql-interfaces@postgresql.org, lbayuk@mindspring.com Subject: Re: still memory leaks with libpgtcl In-reply-to: References: Comments: In-reply-to Gerhard Hintermayer message dated "Wed, 22 Jan 2003 20:39:30 +0100" Date: Fri, 31 Jan 2003 19:08:51 -0500 Message-ID: <1579.1044058131@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/121 X-Sequence-Number: 3621 Gerhard Hintermayer writes: > I found out (actually it was Joe English from TCT), that the segfault > was due to an error in tk (Bug #671330). So I see no reason, why the > above patch should'nt be applied to further releases. I have running > lot's of scripts with the above patch and not having any problem with > both memory leaks or segfaults. Okay, I've applied this patch into CVS head and also REL7_3 branch. It'll be in PG 7.3.2. regards, tom lane