Re: PostgreSQL 8.0.3 Documentation - Chapter 23. Monitoring Database Activity
От | Alvaro Herrera |
---|---|
Тема | Re: PostgreSQL 8.0.3 Documentation - Chapter 23. Monitoring Database Activity |
Дата | |
Msg-id | 20050727040134.GH20145@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: PostgreSQL 8.0.3 Documentation - Chapter 23. Monitoring Database Activity (Halley Pacheco de Oliveira <halleypo@yahoo.com.br>) |
Ответы |
Re: PostgreSQL 8.0.3 Documentation - Chapter 23. Monitoring Database Activity
|
Список | 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)
В списке pgsql-docs по дате отправления: