Re: Accumulating idle processes

On Sun, 2005-11-20 at 22:05 -0800, Gary Hoffman wrote:
> I've run PHP and PostgreSQL for quite a while and never seen this problem
> before. I think it's new, but maybe I never paid attention to it before.
>
> I am frequently running out of connections to the database. Here's a
> snippet of my ps -ax
>
> 1882 ?? S 0:00.07 postgres: postgres cgssd_members [local] idle
>
> 1883 ?? S 0:00.09 postgres: postgres cgssd_members [local] idle
>
> 1884 ?? S 0:00.07 postgres: postgres cgssd_members [local] idle
>
> 1886 ?? S 0:00.14 postgres: postgres cgssd_members [local] idle
>
> 1887 ?? S 0:00.06 postgres: postgres cgssd_members [local] idle
>
> 500 std- S 0:01.14 /usr/local/bin/postmaster -D
> /usr/local/pgsql/data
> 501 std- S 0:00.02 postgres: stats buffer process
>
> 502 std- S 0:00.21 postgres: stats collector process
>
>
> As you can see, there are some connections that have come in from PHP on
> my web pages and have gone idle. I've never seen these before and
> eventually they build up and I get an error connecting from the PHP page
> to the database. I can kill -9 one of them, and the other disappear. What
> is going on here? Some cleanup process is not working.
>
> I'm running Apache 1.3.33 on Darwin Kernal 7.9.0 (MacOS X 10.3.9) with PHP
> 4.3.6 and PostgreSQL 7.4.2.
>
> Ideas and suggestions are welcome.

Are you absolutley sure you close postgres connection within your PHP
pages? I've experienced very same problem using PHP (i was not using
persistent database connections - those seemed much slower) because I
was missing several 'pg_close()' instructions.

The same thing happened to my developers here, using java/tomcat/jdbc to
connect to postgres. Make sure you close all your postgres connections.

Mike
--
Mario Splivalo
Mob-Art
mario(dot)splivalo(at)mobart(dot)hr

"I can do it quick, I can do it cheap, I can do it well. Pick any two."