Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YBovS-0000pC-Rh for pgsql-admin@arkaria.postgresql.org; Thu, 15 Jan 2015 18:13:46 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YBovQ-0002tV-UJ for pgsql-admin@arkaria.postgresql.org; Thu, 15 Jan 2015 18:13:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YBovP-0002tL-PP for pgsql-admin@postgresql.org; Thu, 15 Jan 2015 18:13:43 +0000 Received: from mailout.easymail.ca ([64.68.201.169]) by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YBovH-0000yC-LF for pgsql-admin@postgresql.org; Thu, 15 Jan 2015 18:13:42 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 39BF4E485; Thu, 15 Jan 2015 13:13:21 -0500 (EST) X-Virus-Scanned: Debian amavisd-new at mailout.easymail.ca X-Spam-Flag: NO X-Spam-Score: -4.015 X-Spam-Level: X-Spam-Status: No, score=-4.015 required=5 tests=[ALL_TRUSTED=-1.8, AWL=-0.308, BAYES_00=-2.599, DNS_FROM_AHBL_RHSBL=0.692] Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (easymail-mailout.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AeQGMypeWYhk; Thu, 15 Jan 2015 13:13:20 -0500 (EST) Received: from [192.168.2.16] (unknown [8.39.228.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id A00ECE44D; Thu, 15 Jan 2015 13:13:20 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: PostgreSQL Dump rate is too slow From: Scott Ribe In-Reply-To: Date: Thu, 15 Jan 2015 11:13:19 -0700 Cc: pgsql-admin Content-Transfer-Encoding: quoted-printable Message-Id: References: <20150114212058.de1c87d91a851db0bce1f1fa@yahoo.es> <54B6D972.8010304@commandprompt.com> <54B7FBD9.7080404@commandprompt.com> To: girish R G peetle X-Mailer: Apple Mail (2.1990.1) X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On Jan 15, 2015, at 10:57 AM, girish R G peetle w= rote: >=20 > Thanks Joshua. Even if we have a long transaction running on the database= , pg_dump shouldn't be affected right ? As it doesn't block readers or writ= ers.=20 > Before getting resources to setup stand by server, I just wanna make sure= that we don't this issue on stand by too. I believe he meant that pg_dump itself is the long-running transaction. Eve= n though read-only transactions block neither readers nor writers, they sti= ll prevent cleanup of blocks because they have to be able to see the state = of the db as of the beginning of the transaction. --=20 Scott Ribe scott_ribe@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin