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

Re: Postgres server crash

From: Richard Huxton <dev(at)archonet(dot)com>
To: "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com>
Cc: Russell Smith <mr-russ(at)pws(dot)com(dot)au>,pgsql-performance(at)postgresql(dot)org
Subject: Re: Postgres server crash
Date: 2006-11-16 17:09:45
Message-ID: 455C9B59.7000402@archonet.com (view raw or flat)
Thread:
Lists: pgsql-performance
Craig A. James wrote:
> 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? 

Out Of Memory

 > 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. 

That's 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.

Indeed. See the manuals for details. Section 16.4.3

http://www.postgresql.org/docs/8.1/static/kernel-resources.html#AEN18128

-- 
   Richard Huxton
   Archonet Ltd

In response to

pgsql-performance by date

Next:From: Craig A. JamesDate: 2006-11-16 17:15:54
Subject: Re: Postgres server crash
Previous:From: Craig A. JamesDate: 2006-11-16 17:00:46
Subject: Re: Postgres server crash

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