Juan Miguel writes:
[...]
First.
I have a Linux box with postgres 7.4 branche, where web php applications
queries the DB. When Apache launches a php file that connects to the DB,
if I do "ps aux | grep postgrest", I can see a process "postgres user
...." running, that represents the session openned to the DB. But when
the php program finishes, and closes the connection, this process does
not end. Therefore the number of processes are growing while people
visit the web. ¿ Why ? I see the php code, and there is a closing
command before end.
I see that sometimes I visit a page that connects to the DB and no new
process is performed or remains. I also realise that after several hours
(for example at midnight) those processes don't exist.
What is happening ? Is it usual ? Is there a param to control the number
of process launched and their life times?
In PHP I don't use a pool of connections because, the problem is the
same (there are several processes, and remain after connection closes).
[...]
May be the PHP application uses persistent connections
(http://www.php.net/manual/en/function.pg-pconnect.php)?
--
Milen A. Radev
