Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 0239637B9AE for ; Sun, 28 Sep 2008 06:20:29 -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 80440-01-2 for ; Sun, 28 Sep 2008 06:20:22 -0300 (ADT) Received: from mx1.hub.org (mx1.hub.org [200.46.208.106]) by postgresql.org (Postfix) with ESMTP id 78F2537D2FD for ; Sun, 28 Sep 2008 06:18:30 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.hub.org (Postfix) with ESMTP id 70A35B07419 for ; Sun, 28 Sep 2008 05:23:41 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id 29so201083ugo.7 for ; Sun, 28 Sep 2008 01:23:42 -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:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=JFDCieDjBI6Hvc1mGIiD6HQI6tAM0fXvE8VEvpnZc1Y=; b=Rga1nbN1HYNT8Bxrfo+k8kbNbQvmUhjuoBGX98EzGy4WGgUib0Pr/P52pJEb8mNy57 v+oSU1yRrC6gJXCaDsW1pVYfvfFxYTY7/+KcxhqI5/BMtSgnUjlbDEdCb4DZVAzrFra0 QdonHoIdZ4oeRdxHnfpwYM9H+IgjN+u3er2e0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=vsRIKVTqi0j/LpHupbc2ToJ3Bk5aaNyPrhjOylt5CvW3UIvTvHXoLU/C1suabQNH34 Myj1c3PPAw+GqsN+zuDIXkdqiao2GXRYERg0Gp+qnUmuzLM4BECw2oTkO4p5wk1vep4n wTq3JmgRudCRzsZV3t+eQ4/oGCj1omxss9dXg= Received: by 10.210.44.1 with SMTP id r1mr4252458ebr.153.1222589914798; Sun, 28 Sep 2008 01:18:34 -0700 (PDT) Received: by 10.210.43.4 with HTTP; Sun, 28 Sep 2008 01:18:34 -0700 (PDT) Message-ID: Date: Sun, 28 Sep 2008 10:18:34 +0200 From: "Peter Kovacs" To: "Tom Lane" Subject: Re: Error while trying to back up database: out of memroy Cc: "Vladimir Rusinov" , pgsql-admin@postgresql.org In-Reply-To: <16085.1222094580@sss.pgh.pa.us> 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-Google-Sender-Auth: 1dda317f274e9c82 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/338 X-Sequence-Number: 30431 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.) 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@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin >