Received: from localhost (uranus.hub.org [200.46.204.60]) by postgresql.org (Postfix) with ESMTP id AD54F9FA088 for ; Thu, 16 Nov 2006 13:02:26 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.60]) (amavisd-new, port 10024) with ESMTP id 22527-02-3 for ; Thu, 16 Nov 2006 13:02:22 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from 66-226-76-106.dedicated.abac.net (66-226-76-106.dedicated.abac.net [66.226.76.106]) by postgresql.org (Postfix) with ESMTP id 364A29FA004 for ; Thu, 16 Nov 2006 13:02:21 -0400 (AST) Received: (qmail 24411 invoked by uid 2020); 16 Nov 2006 10:03:15 -0800 Received: from wsip-70-167-125-69.sd.sd.cox.net (HELO ?192.168.0.3?) (70.167.125.69) by 66-226-76-106.dedicated.abac.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 16 Nov 2006 10:03:15 -0800 Message-ID: <455C993E.5050403@modgraph-usa.com> Date: Thu, 16 Nov 2006 09:00:46 -0800 From: "Craig A. James" User-Agent: Thunderbird 1.5.0.8 (X11/20061025) MIME-Version: 1.0 To: Richard Huxton CC: Russell Smith , pgsql-performance@postgresql.org Subject: Re: Postgres server crash References: <20061023215913.GW26892@nasby.net> <20061025001709.GA26892@nasby.net> <453EF7C4.2040105@modgraph-usa.com> <455BCAE8.8010905@modgraph-usa.com> <455BCCCD.2020701@pws.com.au> <455C420D.8090209@archonet.com> In-Reply-To: <455C420D.8090209@archonet.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.798 tagged_above=0 required=5 tests=AWL, BAYES_40, HELO_DYNAMIC_IPADDR2 X-Spam-Level: ** X-Archive-Number: 200611/120 X-Sequence-Number: 21890 Russell Smith wrote: >> For the third time today, our server has crashed... > > I would guess it's the linux OOM if you are running linux. You need to > turn off killing of processes when you run out of memory. Are you > getting close to running out of memory? Good suggestion, it was a memory leak in an add-on library that we plug in to the Postgres server. OOM? Can you give me a quick pointer to what this acronym stands for and how I can reconfigure it? It sounds like a "feature" old UNIX systems like SGI IRIX had, where the system would allocate virtual memory that it didn't really have, then kill your process if you tried to use it. I.e. malloc() would never return NULL even if swap space was over allocated. Is this what you're talking about? Having this enabled on a server is deadly for reliability. Thanks, Craig