| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tony Webb <amw(at)sanger(dot)ac(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Big Delete Consistently Causes a Crash |
| Date: | 2009-07-01 13:56:58 |
| Message-ID: | 10298.1246456618@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tony Webb <amw(at)sanger(dot)ac(dot)uk> writes:
> I have a 8.3 cluster running under VM. It seems fine for most activities
> (a bit slow but error free) but if the developer issues a delete
> statement it consistently kills the database.
>>> 2009-06-25 03:34:26 BST LOG: 00000: server process (PID 8379) was
>>> terminated by signal 9: Killed
Something is issuing kill -9 against random Postgres processes.
If you didn't do it yourself, the odds are about 100% that it was
the Linux kernel's "OOM kill" mechanism, which is best disabled
on any server box.
http://www.postgresql.org/docs/8.3/static/kernel-resources.html#AEN22235
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Juan Camilo Marín | 2009-07-01 15:57:08 | Re: FW: lack in psql console |
| Previous Message | Scot Kreienkamp | 2009-07-01 13:24:41 | Re: WAL and master multi-slave replication |