Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3BE1737B9B3 for ; Mon, 29 Sep 2008 13:36:19 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 82359-02 for ; Mon, 29 Sep 2008 13:36:06 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by postgresql.org (Postfix) with ESMTP id 213F437B9B1 for ; Mon, 29 Sep 2008 13:36:05 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id b25so2003202rvf.43 for ; Mon, 29 Sep 2008 09:36:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=JohCbMDdy94ICnK5dN0Fo64se+GdMthk1MlNaBvZdQs=; b=KDUmlMMs7u5x/5Erdnxc/wGT83qDtjLp5zsWVmjwMLhYAMR/qcdzASih9CstLE4yNX Yy65exuX+FgN22wwMrrQ1I0F4a1/uQS6alsdCBUkWKKhNg3upoksbSs6wXykFn2qggwN /UAO9gHMkfwSC88/NYTTkziS2Vpoa2sFsBUWw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=ukNdPMYmZfkE/Uew81C97vFZgdMZk8OF29rlB77NgCbENwhb/4TJr9+J/LEVwBBDcG F84WYIBsHFw3DqxJwui3BtbmVqcoVBCcmw4apuwUuKx9moT1eBxzV8dDvx/VG4EalCPH HuTaXiyTAfoSIeZp/JmEunvufDbGJdu0gB3fc= Received: by 10.140.139.3 with SMTP id m3mr2616083rvd.165.1222706163416; Mon, 29 Sep 2008 09:36:03 -0700 (PDT) Received: by 10.140.248.12 with HTTP; Mon, 29 Sep 2008 09:36:03 -0700 (PDT) Message-ID: Date: Mon, 29 Sep 2008 10:36:03 -0600 From: "Scott Marlowe" To: "Peter Kovacs" Subject: Re: Error while trying to back up database: out of memroy Cc: "Tom Lane" , "Vladimir Rusinov" , pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <16085.1222094580@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/339 X-Sequence-Number: 30432 On Sun, Sep 28, 2008 at 2:18 AM, Peter Kovacs wrote: > On Mon, Sep 22, 2008 at 4:43 PM, Tom Lane wrote: >> "Vladimir Rusinov" 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.