Skip site navigation (1) Skip section navigation (2)

Re: BUG #2225: Backend crash -- BIG table

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Patrick Rotsaert" <patrick(dot)rotsaert(at)arrowup(dot)be>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2225: Backend crash -- BIG table
Date: 2006-01-31 15:18:06
Message-ID: 3986.1138720686@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Patrick Rotsaert" <patrick(dot)rotsaert(at)arrowup(dot)be> writes:
> At the time of the crash, the server logs:
> 	LOG:  server process (PID 21815) was terminated by signal 9

You're running on a Linux machine with memory overcommit enabled.
Turn that off, or nothing will ever work very reliably --- the OOM
killer is entirely capable of zapping innocent processes that have
nothing to do with the one eating too much memory; and even when it
kills the right process, "kill -9" is not IMHO an acceptable way for
the system to tell a process it can't have any more memory.  See
http://www.postgresql.org/docs/8.1/static/kernel-resources.html#AEN18105

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-01-31 15:39:58
Subject: Re: Endless loop in ExecNestLoop
Previous:From: Philipp ReisnerDate: 2006-01-31 14:32:56
Subject: Re: Endless loop in ExecNestLoop

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group