To: "Bruce Momjian" <bruce@momjian.us>
Cc: "Marshall\, Steve" <smarshall@wsi.com>,  <pgsql-patches@postgresql.org>
Subject: Re: PL/TCL Patch to prevent postgres from becoming multithreaded
In-Reply-To: <200709141720.l8EHKwX13792@momjian.us> (Bruce Momjian's message
	of "Fri\, 14 Sep 2007 13\:20\:58 -0400 \(EDT\)")
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux)
References: <200709141720.l8EHKwX13792@momjian.us>
From: Gregory Stark <stark@enterprisedb.com>
Organization: EnterpriseDB
Date: Fri, 14 Sep 2007 18:50:16 +0100
Message-ID: <87bqc5m90n.fsf@oxford.xeocode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


"Bruce Momjian" <bruce@momjian.us> writes:

> This has been saved for the 8.4 release:
>
> 	http://momjian.postgresql.org/cgi-bin/pgpatches_hold
>
> ---------------------------------------------------------------------------
>
> Marshall, Steve wrote:
>> There is a problem in PL/TCL that can cause the postgres backend to 
>> become multithreaded.   Postgres is not designed to be multithreaded, so 
>> this causes downstream errors in signal handling.  

Um, this is a bug fix. Unless you had some problem with it?

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.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com