Re: large number of connected connections to postgres database (v8.0) - Mailing list pgsql-performance

From Josh Berkus
Subject Re: large number of connected connections to postgres database (v8.0)
Date
Msg-id 200707201628.28266.josh@agliodbs.com
Whole thread Raw
In response to large number of connected connections to postgres database (v8.0)  (Fei Liu <fei.liu@aepnetworks.com>)
List pgsql-performance
Fei Liu,

> It appears my multi-thread application (100 connections every 5 seconds)
> is stalled when working with postgresql database server. I have limited
> number of connections in my connection pool to postgresql to 20. At the
> begining, connection is allocated and released from connection pool as
> postgres serves data request. The pool can recover from exhaustion. But
> very quickly (after about 400 client requests), it seems postgres server
> stops serving and connection to postgres server is not released any more
> resulting a resource exhausting for clients.

This sounds more like a problem with your connection pool.  Unless
PostgreSQL is slowing down due to CPU/RAM/I/O saturation?

In any case, I doubt the problem is too many connections, or you'd just get
an error message ...

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

pgsql-performance by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Postgres configuration for 64 CPUs, 128 GB RAM...
Next
From: "Gavin M. Roy"
Date:
Subject: Re: Postgres configuration for 64 CPUs, 128 GB RAM...