From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Halley Pacheco de Oliveira <halleypo(at)yahoo(dot)com(dot)br> |
Cc: | pgsql-docs(at)postgresql(dot)org, Roman Neuhauser <neuhauser(at)sigpipe(dot)cz> |
Subject: | Re: PostgreSQL 8.0.3 Documentation - Chapter 23. Monitoring Database Activity |
Date: | 2005-07-27 04:01:34 |
Message-ID: | 20050727040134.GH20145@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Tue, Jul 26, 2005 at 10:17:12PM -0300, Halley Pacheco de Oliveira wrote:
> 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.
Hmm, seems a very similar thing can be had in Postgres by means of
pgpool.
It'd be interesting to see how are cursors handled, or any other
long-lived session-local resources for that matter, by this dispatcher
process of Oracle's.
--
Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
"Crear es tan difícil como ser libre" (Elsa Triolet)
From | Date | Subject | |
---|---|---|---|
Next Message | Halley Pacheco de Oliveira | 2005-07-27 12:35:09 | Re: PostgreSQL 8.0.3 Documentation - Chapter 23. Monitoring Database Activity |
Previous Message | Roman Neuhauser | 2005-07-27 01:33:38 | Re: PostgreSQL 8.0.3 Documentation - Chapter 23. Monitoring Database Activity |