From: Mr. Dan <bitsandbytes88@hotmail.com>
To: pgsql-admin@postgresql.org
Subject: could not fork new process for connection: Cannot allocate memory
Date: Tue, 24 Oct 2006 00:48:56 -0400
Message-ID: <BAY116-F17E613460D7DE10BA2A88FD1010@phx.gbl> (raw)
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/minisites/searchlaunch/?locale=en-us&source=hmtagline
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: bitsandbytes88@hotmail.com
Subject: Re: could not fork new process for connection: Cannot allocate memory
In-Reply-To: <BAY116-F17E613460D7DE10BA2A88FD1010@phx.gbl>
References: <BAY116-F17E613460D7DE10BA2A88FD1010@phx.gbl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox