Re: out of memory woes

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Angva <angvaw(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: out of memory woes
Date: 2006-12-29 10:23:57
Message-ID: 20061229102357.GA10785@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Dec 27, 2006 at 07:15:48AM -0800, Angva wrote:
> Just wanted to post an update. Not going too well. Each time the
> scripts were run over this holiday weekend, more statements failed with
> out of memory errors, including more and more create index statements
> (it had only been clusters previously). Eventually, psql could not even
> be called with a very simple one-row update:
>
> psql: could not fork new process for connection: Cannot allocate memory

You have memory overcommit turned off, thus it can't fork a new
process. You must find out what it taking up the virtual memory.

Note that in Linux, overcommit off limits the total virtual memory to
swap space + half of real RAM. How much RAM have you got and how much
active swap? If you have a server with lots of ram, you need at least
half that RAM as swap to be able to use it all...

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andrus 2006-12-29 11:04:08 Re: Why ContinueUpdateOnError is not implemented in npgsql
Previous Message Dave Page 2006-12-29 08:10:21 Re: Backup Restore