Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 5CFCB64FC0D for ; Mon, 22 Sep 2008 11:43:11 -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 87670-08 for ; Mon, 22 Sep 2008 11:43:05 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 055D264FC04 for ; Mon, 22 Sep 2008 11:43:04 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m8MEh0fs016086; Mon, 22 Sep 2008 10:43:00 -0400 (EDT) To: "Vladimir Rusinov" cc: pgsql-admin@postgresql.org Subject: Re: Error while trying to back up database: out of memroy In-reply-to: References: Comments: In-reply-to "Vladimir Rusinov" message dated "Mon, 22 Sep 2008 18:09:13 +0400" Date: Mon, 22 Sep 2008 10:43:00 -0400 Message-ID: <16085.1222094580@sss.pgh.pa.us> From: Tom Lane 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/228 X-Sequence-Number: 30321 "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. 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