Re: LOG: could not fork new process for connection: Cannot allocate memory

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: LOG: could not fork new process for connection: Cannot allocate memory
Date: 2016-08-25 23:51:27
Message-ID: d850ad5e-a2b1-f313-b187-742f500a73a8@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 8/25/2016 3:54 PM, Ahsan Ali wrote:
> Red Hat Enterprise Linux Server release 6.3 (Santiago)

that was released in June 2012, you're missing 4+ years of bug fixes,
6.8 is current.

> max_connections = 3000

thats insanely high for most purposes unless you have several 100 CPU cores.

otherwise, hard to say whats failing, those log entries aren't giving
much info. How many connections are active (select count(*) from
pg_stat_activity; ) when you get the error ?

--
john r pierce, recycling bits in santa cruz

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paquier 2016-08-26 00:05:50 Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed
Previous Message Ahsan Ali 2016-08-25 22:54:34 Re: LOG: could not fork new process for connection: Cannot allocate memory