Home > Archive > PostgreSQL Administration > October 2006 > could not fork new process for connection: Cannot allocate memory









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author could not fork new process for connection: Cannot allocate memory
Mr. Dan

2006-10-25, 8:24 am

Hi,

We are running v814 with 8 GB of RAM and 3.5 GB allocated to shared memory.
It's never been a problem for us before. We ran into a situation
yesterday where we received the message above. At that time our total
available memory took a dive to 4GB and cached memory stayed around 4 GB.
Soon after that some process ended and everything returned to normal. It
alsted around 10 minutes. Too bad I didn't see the query or process at the
time it was running.

~DjK

____________________
____________________
____________________
_____
Try the next generation of search with Windows Live Search today!
http://imagine-windowslive.com/mini...ource=hmtagline


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com