Re: PL/TCL Patch to prevent postgres from becoming multithreaded

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: "Bruce Momjian" <bruce(at)momjian(dot)us>, "Marshall, Steve" <smarshall(at)wsi(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: PL/TCL Patch to prevent postgres from becoming multithreaded
Date: 2007-09-14 17:57:49
Message-ID: 12919.1189792669@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> "Bruce Momjian" <bruce(at)momjian(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-09-14 18:00:41 Re: PL/TCL Patch to prevent postgres from becoming multithreaded
Previous Message Andreas Joseph Krogh 2007-09-14 17:52:31 8.3 version of ts_headline

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2007-09-14 18:00:41 Re: PL/TCL Patch to prevent postgres from becoming multithreaded
Previous Message Gregory Stark 2007-09-14 17:50:16 Re: PL/TCL Patch to prevent postgres from becoming multithreaded