Discussion:
PGSQL-IDLE connection problem
(too old to reply)
Sathish Reddy Yelala
2013-01-28 09:12:19 UTC
Permalink
Hi,

we had problem with <IDLE> connections.when we start the database there
huge number of connections goes to <IDLE> which leads to database access
slow.
How can we prevent the <IDLE> connections and also where we can see the
<IDLE> connection query so that we can identify.
Sathish Reddy Yelala
2013-01-30 07:01:28 UTC
Permalink
hi,

Thanks for the response.Here I have few more queries regarding
Connections.

1.When the connection goes to <IDLE> state
2. when the <IDLE> connection becomes active
3.Is there any chance to database get slow because of <IDLE> connections

Any help would be appreciated..........
Albe Laurenz
2013-01-30 08:08:28 UTC
Permalink
Thanks for the response.Here I have few more queries regarding Connections.
1.When the connection goes to <IDLE> state
When the server has completed a request and waits for
the next one.
2. when the <IDLE> connection becomes active
When the server receives the next request from the client.
3.Is there any chance to database get slow because of <IDLE> connections
It's unlikely, but not impossible, if the idle connections
hog enough system resources to affect the server.
Also a very large value for max_connections might affect
performance of some internal data structures
(see http://wiki.postgresql.org/wiki/Number_Of_Database_Connections).

However, idle connections are not the first place where I would
look for the cause of a performance problem.
Connections "idle in transaction" are more likely to cause trouble.

How big is max_connections?

Yours,
Laurenz Albe
--
Sent via pgsql-admin mailing list (pgsql-***@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Loading...