The surprise is:
Oracle - MTS - Multi-Threaded-Server - MTS allows many user processes to share
very few server
processes. Without MTS, each user process requires its own dedicated server
process; a new server
process is created for each client requesting a connection. A dedicated server
process remains
associated to the user process for the remainder of the connection. With MTS
many user processes
connect to a dispatcher process. The dispatcher routes client requests to the
next available
shared server process. The advantage of MTS is that system overhead is reduced,
so the number of
users that can be supported is increased.
Contrasting with this in PostgreSQL a new process is forked just to connect to
another database.
The PostgreSQL behavior seems similar to old Oracle versions.
Regards,
Halley
--- Roman Neuhauser <[EMAIL PROTECTED]> escreveu:
>
> Well, there's nothing that would make this model required, but it
> surely helps keep things like entropy at reasonable levels.
> IOW, this behavior allows for greater stability through simpler code
> and limited process lifetime.
>
> But maybe I'm not understanding the point you're trying to make.
> To make things a bit clearer: what is it that you find so disturbing
> or surprising in the current PostgreSQL behavior? Why did you expect
> it reusing the same process, and what benefits do you expect (or
> preferably, have experimentally gained) from the alternative?
>
_______________________________________________________
Yahoo! Acesso Grátis - Internet rápida e grátis.
Instale o discador agora! http://br.acesso.yahoo.com/
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
