----- Original Message -----
From: "Greg Copeland" <greg@CopelandConsulting.Net>
Sent: January 03, 2003 4:45 PM
> > > (1) One thread screws up, the whole process dies. In a
> > > multiple process
> > > application this is not too much of an issue.
> >
> > If you use C++ you can try/catch and nothing bad happens to anything but
> > the naughty thread.
>
> That doesn't protect against the type of issues he's talking about.
> Invalid pointer reference is a very common snafu which really hoses
> threaded applications. Not to mention resource leaks AND LOCKED
> resources which are inherently an issue on Win32.
(1) is an issue only for user-level threads. And besides...
----- Original Message -----
From: "Dann Corbit" <DCorbit@connx.com>
Sent: January 03, 2003 3:52 PM
> Here is a solution to the dilemma. Make the one who suggests the
> feature be the first volunteer on the team that writes it.
.. and that's exactly what Shridhar did - he's sent in the code
_already_ in his post, allowing framework to plug in the model
into PG, as he says allowing turning on and off threads where
appropriate and keeping the current model as well. But noone
bothered to go over it if it makes sense.
----- Original Message -----
From: "Greg Copeland" <greg@CopelandConsulting.Net>
Sent: January 03, 2003 4:45 PM
> > Is it a FAQ? If not, it ought to be.
>
> I agree. I think mlw's list of reasons should be added to a faq. It
> terse yet says it all!
<http://developer.postgresql.org/readtext.php?src/FAQ/FAQ_DEV.html+Developers-FAQ#1.9>
But it's not as complete as this threaded thread.
-s