Re: Another 'db session' question...
От | Scott Marlowe |
---|---|
Тема | Re: Another 'db session' question... |
Дата | |
Msg-id | 1092243364.2773.10.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | Another 'db session' question... ("Taber, Mark" <Mark.Taber@dof.ca.gov>) |
Список | pgsql-novice |
On Wed, 2004-08-11 at 08:42, Taber, Mark wrote: > First, thanks for all your responses. The programmers have yet > another question. We will be connecting to a single pg db from our > intranet application (web-based). Each instance of this application > will log on to the database using identical user id’s and passwords > (we have a couple of network and workstation authentications above > this). Each application instance will have its own db session, > correct? (That is, because they will all be connecting to the pg db > with the same user id and password, they won’t share a connection > because of this fact, will they?) Correct. As long as you're not using some form of connection pooling or reuse, each web client will have their own connection. Note that if you're using php, I recommend avoiding pg_pconnect like the plague, unless you know very specifically how to tune apache/php/postgresql to handle the increased number of connections that will remain forever open.
В списке pgsql-novice по дате отправления: