From: | "Angva" <angvaw(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: out of memory woes |
Date: | 2006-12-27 15:15:48 |
Message-ID: | 1167232548.609898.15400@42g2000cwt.googlegroups.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | lopezf@adinet.com.uy | 2006-12-27 16:41:24 | Is PostgreSQL for this? |
Previous Message | Ilja Golshtein | 2006-12-27 14:43:45 | Re: table locks |