From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Viktor *EXTERN*" <viktor(at)okservers(dot)eu>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Random server overload |
Date: | 2013-10-01 15:15:46 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B17C25988@ntex2010a.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Viktor wrote:
> We are experiencing database random overloads caused by IDLE processes.
> Their count jumps from normal ~70 connections to 250-300 with high I/O
> (30-40% wa, when normal ~ 1 % wa).
>
> The overload isn't long and lasts about 5 -10 minutes just a couple of
> times during the month.
>
> Please suggest how to debug this issue and find the cause of the
> overloads. Or mby we should tune our config file ?
>
> errorlog example:
> 2013-09-30 10:37:45 EEST FATAL: sorry, too many clients already
> 2013-09-30 10:37:45 EEST FATAL: remaining connection slots are reserved
> for non-replication superuser connections
Looks like something tries to open lots of connections at these times.
Your best bet is to is to set log_connections = on and examine the log file
when the problem happens. That way you can figure out where the connections
come from.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Jorge Torralba | 2013-10-01 18:18:40 | pg_archivecleanup not cleaning up ? |
Previous Message | Andrew Swartzendruber | 2013-10-01 14:17:37 | pgAdmin forgets password on "could not connect to server" error |