Re: Postgres will not allow new connections, suspended process, waiting error

From: Brian Farrell <brian(dot)farrell(at)vt(dot)edu>
To: Prateek Mahajan <prateekm99(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Postgres will not allow new connections, suspended process, waiting error
Date: 2017-06-30 20:46:06
Message-ID: CAEz6KLW2R+U+veCjpwQNRvBjWOm3hPasVHRZGbkAK5ORU2O_bg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Have you checked to see if you're bumping up against the max_connections
limit?
https://www.postgresql.org/docs/current/static/runtime-config-connection.html#GUC-MAX-CONNECTIONS

-Brian

On Fri, Jun 30, 2017 at 4:39 PM, Prateek Mahajan <prateekm99(at)gmail(dot)com>
wrote:

> We have a recurring problem where Postgres will not allow any new
> connections. Any connection already made keeps working fine. Every time
> this happens, we also have one suspended postgres.exe process that can not
> be cancelled. Also, we get the following error in the logs every minute:
> ‘WARNING: worker took too long to start; canceled’.
>
>
> We’re using Postgres 9.5 on Windows Server 2012 R2. Our original
> hypothesis was that there was something wrong with the autovac settings,
> but we copied the settings over from our other server that does not have
> this problem and still continue to have problem.
>
>
>

--
Brian Farrell
Project Associate
Center for Geospatial Information Technology

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Prateek Mahajan 2017-06-30 21:28:04 Re: Postgres will not allow new connections, suspended process, waiting error
Previous Message Joe Conway 2017-06-30 20:45:24 Re: Postgres vs EnterpriseDB Vulnerability scans with Nessus