Re: out of memory woes - Mailing list pgsql-general

From Angva
Subject Re: out of memory woes
Date
Msg-id 1167232548.609898.15400@42g2000cwt.googlegroups.com
Whole thread Raw
In response to Re: out of memory woes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: out of memory woes  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-general
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

The logs are nothing but this message repeated at this point:

<2006-12-26 00:00:01 EST>LOG:  could not fork new process for
connection: Cannot allocate memory
<2006-12-26 00:00:01 EST>LOG:  could not fork new process for
connection: Cannot allocate memory
<2006-12-26 00:00:01 EST>LOG:  could not fork new process for
connection: Cannot allocate memory
<2006-12-26 00:00:01 EST>LOG:  could not fork new process for
connection: Cannot allocate memory
<2006-12-26 02:00:01 EST>LOG:  could not fork new process for
connection: Cannot allocate memory
<2006-12-26 02:00:01 EST>LOG:  could not fork new process for
connection: Cannot allocate memory
<2006-12-26 02:00:01 EST>LOG:  could not fork new process for
connection: Cannot allocate memory

I think I'm about ready to bounce the server every night unfortunately.

Thanks for listening,
Mark


pgsql-general by date:

Previous
From: "karthik"
Date:
Subject: could not open relation:no such file or directory
Next
From: "Stuart Grimshaw"
Date:
Subject: Re: ERROR: could not access status of transaction