postgres connection question

[zeropaid]

Can I use pg_close() to kill any open connections in a php include? I'm having trouble with to idling connections. I've read about php closing open connections, but was unsure if this applied in postgres.

Thanks.

[[deleted]]

WHen a script ends PHP always closes all the connections it has opened, unless you use pconnect. If you use pconnect to open the connection, then nothing can close it. The connection will close automatically after a timeout that is defined in php.ini.

Also, be sure that you don't confuse idle connections with idle backends. databases can keep backends alive to avoid having to start up new backends all the time,

[zeropaid]

Ok, that seems to make sense. Thanks for the info.

After reviewing the code again, I found the provious web developer was using pg_pconnect(), which I would assume is PostgreSQL's version of pconnect leading to the problem.

To many connections, (32)
simutanious connections

[Sxooter]

Originally posted by zeropaid
Ok, that seems to make sense. Thanks for the info.

After reviewing the code again, I found the provious web developer was using pg_pconnect(), which I would assume is PostgreSQL's version of pconnect leading to the problem.

To many connections, (32)
simutanious connections

Yep. Postgresql comes outta the box set for workstation type loads, and so is limited to 32 connects. You can increase the number by editing the $PGDATA/postgresql.conf file, but the best answer is to just not use pconnect unless you have to, and by then, you'll have plenty of experience with apache/php/postgresql and a very heavily loaded server.