Skip site navigation (1) Skip section navigation (2)

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Marshall, Steve" <smarshall(at)wsi(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: PL/TCL Patch to prevent postgres from becoming multithreaded
Date: 2007-09-21 00:32:57
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
"Marshall, Steve" <smarshall(at)wsi(dot)com> 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.  We have seen this 
> cause a number of "unexpected state" errors associated with notification 
> handling; however, unpredictable signal handling would be likely to 
> cause other errors as well. 

I've applied this patch to CVS HEAD (8.3-to-be).  I'm a bit hesitant
to back-patch it however, at least not till it gets through some beta

Thanks for the detailed explanation, test case, and patch!

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Neil ConwayDate: 2007-09-21 00:34:32
Subject: Re: stored procedure stats in collector
Previous:From: Tom RaneyDate: 2007-09-21 00:12:45
Subject: Re: Hash index todo list item

pgsql-patches by date

Next:From: Joshua D. DrakeDate: 2007-09-21 00:42:10
Subject: Patch to update log levels
Previous:From: Andrew DunstanDate: 2007-09-20 19:11:51
Subject: Re: Various fixes for syslogger

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group