Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 50BA91337B9C for ; Tue, 15 Feb 2011 14:41:21 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 42056-01-7 for ; Tue, 15 Feb 2011 18:41:11 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from a2s33.a2hosting.com (a2s33.a2hosting.com [216.119.140.194]) by mail.postgresql.org (Postfix) with ESMTP id 849C21337C28 for ; Tue, 15 Feb 2011 14:41:04 -0400 (AST) Received: from localhost ([127.0.0.1] helo=anticentertainment.com) by a2s33.a2hosting.com with esmtpa (Exim 4.69) (envelope-from ) id 1PpPpg-0005v4-7h for pgsql-performance@postgresql.org; Tue, 15 Feb 2011 13:41:04 -0500 MIME-Version: 1.0 Date: Tue, 15 Feb 2011 13:41:04 -0500 From: Mark Mikulec To: Subject: =?UTF-8?Q?pg=5Fdumpall=20affecting=20performance?= Organization: Antic Entertainment Message-ID: X-Sender: mark@anticentertainment.com User-Agent: RoundCube Webmail/0.3.1 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a2s33.a2hosting.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - anticentertainment.com X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201102/394 X-Sequence-Number: 42532 Hello, I was under the impression that pg_dumpall didn't affect database performance when dumping while the db is live. However I have evidence to the contrary now - queries that are run during the pg_dumpall time take 10 to a 100 times longer to execute than normal while pg_dumpall is running. The strange thing is that this started after my database grew by about 25% after a large influx of data due to user load. I'm wonder if there is a tipping point or a config setting I need to change now that the db is larger that is causing all this to happen. Thanks, Mark