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 p
# [EMAIL PROTECTED] / 2005-07-26 22:17:12 -0300:
> --- Roman Neuhauser <[EMAIL PROTECTED]> escreveu:
> > 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
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
proce
# [EMAIL PROTECTED] / 2005-07-26 14:17:17 -0300:
> What surprises me is not that the previous connection is closed and a
> new connection is opened.
> What surprises me is the fact that the previous process is killed and
> a new process is forked just to connect to another database with the
> same
What surprises me is not that the previous connection is closed and a new
connection is opened.
What surprises me is the fact that the previous process is killed and a new
process is forked just
to connect to another database with the same user. I was expecting that the new
connection could
use
# [EMAIL PROTECTED] / 2005-07-26 13:48:55 +:
> --- Peter Eisentraut <[EMAIL PROTECTED]> escreveu:
>
> > Am Dienstag, 26. Juli 2005 12:06 schrieb Halley Pacheco de Oliveira:
> > > The user, database, and connection source host items remain the same for
> > > the life of the client connection, b
There is no problem, just a surprise. Once I was connected to one database I
didn't expect that a
connection to another database inside psql would close one process and fork a
new process. Once
the chapter is about Monitoring Database Activity, I think that it would be
good to alert the
readers
Am Dienstag, 26. Juli 2005 12:06 schrieb Halley Pacheco de Oliveira:
> The user, database, and connection source host items remain the same for
> the life of the client connection, but the activity indicator changes.
> So the database name didn't remain the same, neither the process id.
> Connecti
In PostgreSQL 8.0.3 Documentation - Chapter 23. Monitoring Database Activity -
23.1. Standard Unix
Tools is written:
The user, database, and connection source host items remain the same for the
life of the client
connection, but the activity indicator changes.
But look at that:
psql -U sistema
