On 05-07-2012 00:28:15 -0700, Tapomay Dey wrote:
2012-07-05 06:30:59 MSG merovingian[31153]: database 'tablename' (1048) was killed by signal SIGKILL
mserver5 gets KILLed here. (SIGKILL is usually 9, deadly, cannot be handled by the process). Most likely your operating system doesn't like mserver5 here, and just kills it. Check your /var/log/messages (or alike) for OOM kills.
Is there a config that would ask mserver to not kill itself and keep processing at the cost of query execution time.
It doesn't kill itself, you or your operating system are killing it. In the upcoming Jul2012 release we did a fair bit of work on memory management, and better behaviour by letting the operating system choose for itself what it seems best to do. It would be interesting if you could try out the (still under development, no release candidates yet -- should come really soon) Jul2012 branch, e.g. by compiling http://monetdb.cwi.nl/testweb/web/44451:5aebbb6f96b0/MonetDB-11.11.0.tar.bz2 Looking forward hearing if that makes any difference for you, Fabian