Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VRHY1-00084A-VZ for pgsql-admin@arkaria.postgresql.org; Wed, 02 Oct 2013 08:12:42 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VRHY1-0000nI-F9 for pgsql-admin@arkaria.postgresql.org; Wed, 02 Oct 2013 08:12:41 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VRHY0-0000nC-MD for pgsql-admin@postgresql.org; Wed, 02 Oct 2013 08:12:40 +0000 Received: from mail-out.elkdata.ee ([195.250.189.24]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VRHXw-0004hq-Gk for pgsql-admin@postgresql.org; Wed, 02 Oct 2013 08:12:40 +0000 Received: from mail.elkdata.ee (mail.elkdata.ee [194.106.101.168]) by mail-out.elkdata.ee (Postfix) with ESMTP id 3BB7364EADE3 for ; Wed, 2 Oct 2013 11:12:35 +0300 (EEST) Received: from [10.0.1.204] (unknown [195.222.11.180]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.elkdata.ee (Postfix) with ESMTPSA id 190D867C4774 for ; Wed, 2 Oct 2013 11:12:34 +0300 (EEST) Message-ID: <524BD56C.7030900@okservers.eu> Date: Wed, 02 Oct 2013 11:12:28 +0300 From: Viktor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Random server overload References: <524ACBD0.5000400@okservers.eu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -0.0 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On 10/1/2013 4:45 PM, Igor Neyman wrote: > Did you try using any kind of connection pooler, e.g. PgBouncer? > Should help. Our Java application uses c3p0 connection pooler and we don't think that it's the issue. On 10/1/2013 6:15 PM, Albe Laurenz wrote: > 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 I have made the changes to the config file and will update this ticket later with the results. Thank you all! -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin