Re: PL/TCL Patch to prevent postgres from becoming multithreaded - Mailing list pgsql-patches

From Stefan Kaltenbrunner
Subject Re: PL/TCL Patch to prevent postgres from becoming multithreaded
Date
Msg-id 46EADA0A.3040504@kaltenbrunner.cc
Whole thread Raw
In response to Re: PL/TCL Patch to prevent postgres from becoming multithreaded  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PL/TCL Patch to prevent postgres from becoming multithreaded
List pgsql-patches
Tom Lane wrote:
> Gregory Stark <stark@enterprisedb.com> writes:
>> "Bruce Momjian" <bruce@momjian.us> writes:
>>>> 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?
>
> I haven't reviewed that patch yet, but I concur we should consider it
> for 8.3.

hmm i wonder if that could be related to:

http://archives.postgresql.org/pgsql-hackers/2007-01/msg00377.php


Stefan

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: PL/TCL Patch to prevent postgres from becoming multithreaded
Next
From: Tom Lane
Date:
Subject: Re: PL/TCL Patch to prevent postgres from becoming multithreaded