Postgres Pro
Downloads
Home   >   mailing lists

Re: Random server overload - Mailing list pgsql-admin

From Viktor Juhanson
Subject Re: Random server overload
Date
Msg-id 1381238407.439eeaea@webmail.zone.ee
Whole thread Raw
In response to pg_stat_activity - proc id  ("Rajagopalan, Jayashree" <Jayashree.Rajagopalan@emc.com>)
Responses Re: Random server overload  (Kevin Grittner <kgrittn@ymail.com>)
List pgsql-admin
Tree view
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?

pgsql-admin by date:

Previous
From: Matheus de Oliveira
Date:
Subject: Re: Reg. Restore
Next
From: Kevin Grittner
Date:
Subject: Re: Random server overload