From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Sam <sam(at)palo-verde(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Help me stop postgres from crashing. |
Date: | 2010-04-24 23:13:58 |
Message-ID: | 15314.1272150838@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Sam <sam(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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-04-25 01:01:39 | Re: Identical command-line command will not work with \i metacommand and filename |
Previous Message | Fredric Fredricson | 2010-04-24 23:09:23 | Re: How to allow PostgreSQL to accept remote connection? |