Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 923CD650038 for ; Wed, 27 Aug 2008 14:42:01 -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 47522-05 for ; Wed, 27 Aug 2008 14:41:57 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228]) by postgresql.org (Postfix) with ESMTP id 524B464FCF3 for ; Wed, 27 Aug 2008 14:41:58 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id b25so4049906rvf.43 for ; Wed, 27 Aug 2008 10:41:56 -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:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ACYS5hd+svrccQHWXDCgYhU9R6TUgaztP3gKDnolGsE=; b=IdrKkgMcJkKSGR4CaliTqtryUvU9wy0d8pxqTOIpe9H5/P1tUxhS4EJ8Lw/3RrgEWN ISuwZs4WChh4fteJWRnPIpfl2fwnXoHHFzR92JL548yEnrBUBvrH+OfKYk6FOjtmwAEN d/pkmL39HG9tlkWGoAHwYgHRrDDq2UWt50rQM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=MRE8ksiyhRGmEb+sQmx3TgHsJhpwFskB9FBhh6MFGTfNiuyMjbZBvI6OV31cb2pI5E WsA4P6cHU9mZiBKYgK3cIF5NrTPBXLf6FfQxyg8taZKU7IUL7wkMhGUaTPIUoVx3JhwT EZvn7SFds5jfUIfmQ6A1QDyybNZWTo/SonqwE= Received: by 10.141.78.14 with SMTP id f14mr159434rvl.76.1219858916187; Wed, 27 Aug 2008 10:41:56 -0700 (PDT) Received: by 10.141.197.1 with HTTP; Wed, 27 Aug 2008 10:41:56 -0700 (PDT) Message-ID: Date: Wed, 27 Aug 2008 11:41:56 -0600 From: "Scott Marlowe" To: "Phoenix Kiula" Subject: Re: Dumping/Restoring with constraints? Cc: "Bill Moran" , "PG-General Mailing List" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <22708.1219845242@sss.pgh.pa.us> <20080827102403.dc69c802.wmoran@collaborativefusion.com> <20080827103429.081e93a1.wmoran@collaborativefusion.com> 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: 200808/966 X-Sequence-Number: 136796 On Wed, Aug 27, 2008 at 8:40 AM, Phoenix Kiula wrote: > Thanks. But there seems to be a tangible slowdown of DB operations > during the time that pg_dump is running. Perhaps some of my > postgresql.conf variables are not geared to this. (I vaguely recall > setting it up so that the wal_buffers or checkpoint_segments needed to > be set upwards for maintenance tasks). > > My question: is it possible to interactively set up these variables so > that pg_dumpall can work very fast? And behind the scenes, without > slowing stuff down? Nope, it's not a software problem, it's a hardware problem. You're drive subsystem can only deliver data so fast. The fix is usually better hardware. Big RAID controller and lots of drives.