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

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, 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 18:59:22
Message-ID: 46EADA0A.3040504@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> 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.

hmm i wonder if that could be related to:

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

Stefan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2007-09-14 18:59:40 Re: RETURNING and DO INSTEAD ... Intentional or not?
Previous Message Bruce Momjian 2007-09-14 18:50:58 Re: RETURNING and DO INSTEAD ... Intentional or not?

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-09-15 01:53:28 Re: PL/TCL Patch to prevent postgres from becoming multithreaded
Previous Message Bruce Momjian 2007-09-14 18:07:30 Re: PL/TCL Patch to prevent postgres from becoming multithreaded