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

"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
testing.

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

regards, tom lane