From: Viktor <viktor@okservers.eu>
To: pgsql-admin@postgresql.org
Subject: Re: Random server overload
Date: Wed, 02 Oct 2013 11:12:28 +0300
Message-ID: <524BD56C.7030900@okservers.eu> (raw)
In-Reply-To: <A76B25F2823E954C9E45E32FA49D70EC42823C34@mail.corp.perceptron.com>
References: <524ACBD0.5000400@okservers.eu>
<A76B25F2823E954C9E45E32FA49D70EC42823C34@mail.corp.perceptron.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: viktor@okservers.eu
Subject: Re: Random server overload
In-Reply-To: <524BD56C.7030900@okservers.eu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox