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

Re: Error while trying to back up database: out of memroy

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Peter Kovacs" <peter(dot)kovacs(dot)1(dot)0rc(at)gmail(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Vladimir Rusinov" <vladimir(at)greenmice(dot)info>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Error while trying to back up database: out of memroy
Date: 2008-09-29 16:36:03
Message-ID: dcc563d10809290936g1e3085c1sa8b7fb87930cc07e@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Sun, Sep 28, 2008 at 2:18 AM, Peter Kovacs
<peter(dot)kovacs(dot)1(dot)0rc(at)gmail(dot)com> wrote:
> On Mon, Sep 22, 2008 at 4:43 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> "Vladimir Rusinov" <vladimir(at)greenmice(dot)info> writes:
>>> But now I'm getting following error:
>>> pg_dump: WARNING:  terminating connection because of crash of another server
>>> process
>>
>> As a rule of thumb, you should disable OOM kill on any server system.
>
> This document describes a few solutions potentially better than
> outright disabling:
> http://www.redhat.com/archives/taroon-list/2007-August/msg00006.html .
> (I don't know whether those solutions actually work or not, but may be
> worth trying by the look of it.)

While there are better solutions for other types of servers, like web
servers and what not, for PostgreSQL servers, overcommit isn't usually
needed, and OOM killer / overcommit can both be disabled.

In response to

pgsql-admin by date

Next:From: Andrew SullivanDate: 2008-09-29 17:02:57
Subject: Re: turning of pg_xlog
Previous:From: Tom LaneDate: 2008-09-29 14:23:36
Subject: Re: understand the process of ID wraparound

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