Postgres Pro
Downloads
Home   >   mailing lists

Re: LOG: could not fork new process for connection: Cannot allocate memory - Mailing list pgsql-general

From John R Pierce
Subject Re: LOG: could not fork new process for connection: Cannot allocate memory
Date
Msg-id d850ad5e-a2b1-f313-b187-742f500a73a8@hogranch.com
Whole thread Raw
In response to Re: LOG: could not fork new process for connection: Cannot allocate memory  (Ahsan Ali <ali95695@gmail.com>)
Responses Re: LOG: could not fork new process for connection: Cannot allocate memory  (Ahsan Ali <ali95695@gmail.com>)
List pgsql-general
Tree view
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

pgsql-general by date:

Previous
From: Ahsan Ali
Date:
Subject: Re: LOG: could not fork new process for connection: Cannot allocate memory
Next
From: Michael Paquier
Date:
Subject: Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed