Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id B91BB64FCDA for ; Wed, 27 Aug 2008 11:40:47 -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 34115-08 for ; Wed, 27 Aug 2008 11:40:37 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by postgresql.org (Postfix) with ESMTP id 67D9064FCD4 for ; Wed, 27 Aug 2008 11:40:43 -0300 (ADT) Received: by nf-out-0910.google.com with SMTP id c7so1163741nfi.23 for ; Wed, 27 Aug 2008 07:40:41 -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=vVMVpcW4Lle8pq01fuB3GdEAZrL+LER/RpT2jrsTHec=; b=wdXSy82TSFQOvLhDoTReTCyr0aB+IlbSykqEA8WL0Nq40Na///0Z9rnQHQlTp8ttxY yD3KDGr/i1Q1jVTcB3753nK12hQah8crVzVNRN2NUXg/86cR4Wzfuy7nTVSK6/bYwHSL AJZJz0I9PMzMSmFHw8qDBis+QzqVsZNvRHx8M= 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=J+r/bAoBr+KCsITLvPsVVHjWkF+QMCZK4HUtalGx9TVEOxmM/Wh8nBqUi0uCVshSYd aQMw9fKbUpK4BlvsZaaDLRH3TE1NFYPk+o0f2gARlHQja+iGHkBC3+1ODMDj16XGLT8N 5AgU9bXqO435zq3MBNYQwc6zR5UQ3cjBe1pdE= Received: by 10.210.51.10 with SMTP id y10mr44344eby.34.1219848041193; Wed, 27 Aug 2008 07:40:41 -0700 (PDT) Received: by 10.210.130.1 with HTTP; Wed, 27 Aug 2008 07:40:41 -0700 (PDT) Message-ID: Date: Wed, 27 Aug 2008 22:40:41 +0800 From: "Phoenix Kiula" To: "Bill Moran" Subject: Re: Dumping/Restoring with constraints? Cc: "PG-General Mailing List" In-Reply-To: <20080827103429.081e93a1.wmoran@collaborativefusion.com> 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/951 X-Sequence-Number: 136781 On Wed, Aug 27, 2008 at 10:34 PM, Bill Moran wrote: >> >> >> Dumb question. Will this kind of pg_dumpall lead to downtime, I mean >> is there a database lock during this time? > > No. 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? Thanks