	*snip*
> > 
> > Once all the questions regarding "why not" have been answered, it would
> > be good to also ask "why use threads?"  Do they simplify the code?  Do
> > they offer significant performance or efficiency gains?  What do they
> > give, other than being buzzword compliant?
> 
	The primary advantage that I see is that a single postgres process
can benefit from multiple processors. I see little advantage to using thread
for client connections.

Mon, 4 Dec 2000 17:48:36 -0600 
Matthew <matt@ctlno.com>
RE: Using Threads?
Matthew wrote:
>         The primary advantage that I see is that a single postgres process
> can benefit from multiple processors. I see little advantage to using thread
> for client connections.

Multiprocessors best benefit multiple backends.  And the current forked
model lends itself admirably to SMP.

And I say that even after using a multithreaded webserver (AOLserver)
for three and a half years.  Of course, AOLserver also sanely uses the
multi process PostgreSQL backends in a pooled fashion, but that's beside
the point.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

Mon, 04 Dec 2000 20:18:44 -0500
Lamar Owen <lamar.owen@wgcr.org>
Re: Using Threads?