I've seen this quite a bit lately especially when Vmware is involved. Over committing the host server is becoming more common and Vmware has this "balloon" driver which can bring out the Linux oom-killer process. Check your messages file for "oom-killer". If it's there, Tom's right and you need to check into tweaking the kernel a little. sysctl -w vm.overcommit_memory=2 OR echo "vm.overcommit_memory=2" >> /etc/sysctl.conf sysctl -p Greg -----Original Message----- From: pgsql-admin-owner@xxxxxxxxxxxxxx [mailto:pgsql-admin-owner@xxxxxxxxxxxxxx] On Behalf Of Tom Lane Sent: Monday, January 28, 2008 4:27 PM To: dx k9 Cc: posgres support Subject: Re: Zen and art if WAL and dump file mainteance dx k9 <bitsandbytes88@xxxxxxxxxxx> writes: > We are trying to figure out why maintenance on A (zipping up & removing files) would have an affect on production processing (killed it) on pgdata - B. Sounds like an OOM kill problem --- do you have memory overcommit disabled on that machine? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your message can get through to the mailing list cleanly CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error; please notify Cranel Incorporated immediately by telephone at 614-431-8000 or 800-288-3475 and destroy all copies of this communication and any attachments. ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your message can get through to the mailing list cleanly
