From: | Samuel <sam(at)palo-verde(dot)us> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Help me stop postgres from crashing. |
Date: | 2010-04-25 17:59:03 |
Message-ID: | 012bec30-129f-4eda-8059-1a330b78790c@x18g2000prk.googlegroups.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Apr 24, 4:13 pm, t(dot)(dot)(dot)(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) wrote:
> Sam <s(dot)(dot)(dot)(at)palo-verde(dot)us> writes:
> > A particular web application I am working has a staging version
> > running one a vps, and a production version running on another vps.
> > They both get about the same usage, but the production version keeps
> > crashing and has to be re-started daily for the last couple days. The
> > log file at the time of crash looks like this:
> > LOG: could not accept new connection: Cannot allocate memory
> > LOG: select() failed in postmaster: Cannot allocate memory
>
> This looks like a system-level memory shortage. You might find useful
> information in the kernel log. I'd suggest enabling timestamps in the
> PG log (see log_line_prefix) so that you can correlate events in the
> two log files.
>
> regards, tom lane
>
> --
> Sent via pgsql-general mailing list (pgsql-gene(dot)(dot)(dot)(at)postgresql(dot)org)
> To make changes to your subscription:http://www.postgresql.org/mailpref/pgsql-general
Thanks, for the responses.
I've enabled the timestamps on the log lines.
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Ross | 2010-04-25 18:00:25 | Plpgsql function syntax error at first coalesce statement |
Previous Message | Samuel | 2010-04-25 17:57:27 | Re: Help me stop postgres from crashing. |