Postgres Pro
Downloads
Home   >   mailing lists

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

From Ahsan Ali
Subject LOG: could not fork new process for connection: Cannot allocate memory
Date
Msg-id CAGot2LWkLJ35raUwYbjj6h0ZhKEn7i+eomOgTJexb_30peJceQ@mail.gmail.com
Whole thread Raw
Responses Re: LOG: could not fork new process for connection: Cannot allocate memory  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
Tree view
Hi Support

I having my production server service intruption because of this "Cannot allocate memory" error in the db log. 

because of this error even DBA's cant login to the db server unless we kill one of the existing sessions. Please help me resolve this issue.

  1. $ grep Commit /proc/meminfo
  2. CommitLimit:    133625220 kB
  3. Committed_AS:   82635628 kB
  4.  
  5.  
  6. $ cat /proc/sys/vm/overcommit_memory
  7. 2
  8.  
  9.  
  10.  
  11. $ free -m -g
  12.              total       used       free     shared    buffers     cached
  13. Mem:           252        238         13          0          0        175
  14. -/+ buffers/cache:         62        189
  15. Swap:            7          0          7

pgsql-general by date:

Previous
From: Theron Luhn
Date:
Subject: Re: Understanding Postgres Memory Usage
Next
From: Tom Lane
Date:
Subject: Re: Understanding Postgres Memory Usage