Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Robert Klemme <shortcutter@googlemail.com>
Newsgroups: comp.databases.postgresql
Subject: Re: Pg_dump makes me nut !
Date: Sat, 19 Dec 2015 21:38:39 +0100
Lines: 16
Message-ID: <ddltigFj5knU1@mid.individual.net>
References: <n50sgh$a4c$1@speranza.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net k5zOKv25fPmvyD/W632Xhgqb4Hl5epu7a5FjCvIFOssdKMVZY=
Cancel-Lock: sha1:Cz7j+mp4I7iXAL1afbOZJkIHuxY=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
In-Reply-To: <n50sgh$a4c$1@speranza.aioe.org>
Xref: csiph.com comp.databases.postgresql:689

On 18.12.2015 13:00, DeepThought wrote:

> How may can I limit pg_dump memory consumption to  fit my resources?

Just a wild guess: maybe you memory settings are generally way off, i.e. 
you have configured the DB to use too much mem as max and the max is not 
reached during regular operations.

Kind regards

	robert


-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/