pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gerhard Hintermayer <g.hintermayer@inode.at>
Cc: pgsql-interfaces@postgresql.org
Cc: lbayuk@mindspring.com
Subject: Re: still memory leaks with libpgtcl
Date: Fri, 31 Jan 2003 19:08:51 -0500
Message-ID: <1579.1044058131@sss.pgh.pa.us> (raw)
In-Reply-To: <b0mscn$1iko$1@news.hub.org>
References: <as0da6$2njk$1@news.hub.org>
	<auhq8v$2iuo$1@news.hub.org>
	<auj41k$f4v$1@news.hub.org>
	<avf32e$rep$1@news.hub.org>
	<avg4mq$1ikp$1@news.hub.org>
	<bd4db85f.0301160134.499958fb@posting.google.com>
	<b0mscn$1iko$1@news.hub.org>

Gerhard Hintermayer <g.hintermayer@inode.at> 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



view thread (15+ messages)

Message-ID: <1579.1044058131@sss.pgh.pa.us>
Permalink:  ../1579.1044058131@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1579.1044058131@sss.pgh.pa.us

 · 

reply

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, g.hintermayer@inode.at, lbayuk@mindspring.com
  Subject: Re: still memory leaks with libpgtcl
  In-Reply-To: <1579.1044058131@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