From: Viktor Juhanson <spoon@planet.ee>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Random server overload
Date: Tue, 08 Oct 2013 16:20:07 +0300
Message-ID: <1381238407.439eeaea@webmail.zone.ee> (raw)
In-Reply-To: <A7A2044B8A59DA4F9F07599B3B1CA1210E4CB4A7@MX101CL02.corp.emc.com>
References: <A7A2044B8A59DA4F9F07599B3B1CA1210E4CB4A7@MX101CL02.corp.emc.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Hello,
It's me again..
Log_connection inspection didn't help to find the cause, the connections come from our app-servers as usual..
Btw we have the max pool size of web application 50 connections and since we have 4 instances of application running it makes max 200.
I don't really get how the database pool gets full when application can use 200 connections max and postrgesql config has set to 250 max connections ?
Autovacuum and master-slave replication shouldn't use many connections also.
Please explain that, maybe i'm missing something.
Should we try to reduce this limit to 40 per application?
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: spoon@planet.ee
Subject: Re: Random server overload
In-Reply-To: <1381238407.439eeaea@webmail.zone.ee>
* 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