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

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

From: "Peter Kovacs" <peter(dot)kovacs(dot)1(dot)0rc(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "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-28 08:18:34
Message-ID: b6e8f2e80809280118r39b38e95rbbcc9dd5b8b54a38@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
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.)

Peter

> However, you might want to look into why the system's aggregate memory
> requirements have now increased from what they used to be.  It seems
> unlikely that this is pg_dump's fault per se, if you're running a
> reasonably recent PG release.  (There were some memory leaks inside
> pg_dump, a long time ago...)
>
>                        regards, tom lane
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>

In response to

Responses

pgsql-admin by date

Next:From: Matthew PulisDate: 2008-09-29 04:43:52
Subject: PostgreSQL Cache
Previous:From: Michelle KonzackDate: 2008-09-27 15:24:15
Subject: Re: Hex representation

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