Re: BUG #2225: Backend crash -- BIG table - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #2225: Backend crash -- BIG table
Date
Msg-id 3986.1138720686@sss.pgh.pa.us
Whole thread Raw
In response to BUG #2225: Backend crash -- BIG table  ("Patrick Rotsaert" <patrick.rotsaert@arrowup.be>)
Responses Re: BUG #2225: Backend crash -- BIG table
List pgsql-bugs
"Patrick Rotsaert" <patrick.rotsaert@arrowup.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

pgsql-bugs by date:

Previous
From: "Patrick Rotsaert"
Date:
Subject: BUG #2225: Backend crash -- BIG table
Next
From: Tom Lane
Date:
Subject: Re: Endless loop in ExecNestLoop