Message-ID: <46EACC49.3060404@dunslane.net>
Date: Fri, 14 Sep 2007 14:00:41 -0400
From: Andrew Dunstan <andrew@dunslane.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.8.0.12) Gecko/20070719 Fedora/1.0.9-2.fc6 pango-text
	SeaMonkey/1.0.9
MIME-Version: 1.0
To: Gregory Stark <stark@enterprisedb.com>
CC: Bruce Momjian <bruce@momjian.us>, "Marshall\, Steve" <smarshall@wsi.com>,
	pgsql-patches@postgresql.org
Subject: Re: PL/TCL Patch to prevent postgres from becoming multithreaded
References: <200709141720.l8EHKwX13792@momjian.us>
	<87bqc5m90n.fsf@oxford.xeocode.com>
In-Reply-To: <87bqc5m90n.fsf@oxford.xeocode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Gregory Stark wrote:
> Do we have anyone actively maintaining pltcl these days? I'm intentionally
> quite unfamiliar with Tcl or I would be happy to verify it's reasonable. But
> the explanation seems pretty convincing. If we don't have anyone maintaining
> it then we're pretty much at the mercy of applying whatever patches come in
> from people who are more familiar with it than us. In my experience that's how
> new maintainers for modules of free software are often found anyways.
>
>   

I was hoping that Jan or somebody else with some Tcl-fu would comment. I 
agree it probably shouldn't be deferred.

It does bother me a bit that the Tcl engine startup just starts firing 
up threads without advertisement - I wondered if we shouldn't kick back 
and say it's their problem to fix.

cheers

andrew