| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Sandeep Gupta <gupta(dot)sandeep(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: what could cause postgres to crash? |
| Date: | 2013-11-09 03:26:28 |
| Message-ID: | 4969.1383967588@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Sandeep Gupta <gupta(dot)sandeep(at)gmail(dot)com> writes:
> My postgres sessions, after being idle for 5 --6 hrs, crash on their own.
> Sometimes with error messages sometimes without. The message I get appended
> below. I was looking for suggestion to narrow down as to what could have
> caused this problem. System log doesn't show anything.
> LOG: statistics collector process (PID 6631) was terminated by signal 9:
> Killed
Signal 9 is a kill. If you didn't manually kill the process, it's almost
certainly the infamous Linux OOM killer that did it. And yes, that would
be recorded in the kernel log ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jayadevan M | 2013-11-09 07:23:55 | Documents/ppts/pdfs |
| Previous Message | Sandeep Gupta | 2013-11-09 03:16:40 | what could cause postgres to crash? |