Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id A991364FCD4
	for <pgsql-general-postgresql.org@postgresql.org>;
	Wed, 27 Aug 2008 11:26: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 21219-07 for
	<pgsql-general-postgresql.org@postgresql.org>;
	Wed, 27 Aug 2008 11:26:34 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153])
	by postgresql.org (Postfix) with ESMTP id 7F308650014
	for <pgsql-general@postgresql.org>;
	Wed, 27 Aug 2008 11:26:40 -0300 (ADT)
Received: by fg-out-1718.google.com with SMTP id 16so1860741fgg.23
	for <pgsql-general@postgresql.org>;
	Wed, 27 Aug 2008 07:26:38 -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=1/uWsOVFsyz/kfrVMmkPtAtGj1a8mQMHROpKj1ap8Y0=;
	b=H0T2YQvY5SWoBvOu4V1/iWoNFqP1zfZ7Qm39Hsrr2/Z9XCzaWDO3RQOVBipxj9xffH
	EuF588JMR0Lg8Q8M4i+9+bnloyGeAVxgF8mq1hzKZyTJFRcOIcdLKDlLAyeHz7pfvbou
	01SpOcZ+Pg05nd8U5lQ2nv19iq0T2NG3NhHvw=
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=If77P05zIcUlFEFcR/Xu8E4huZK93tZBuH2FRtBZT3CD3m236ipEaJgeAHHn2dBJbO
	QTPzw6sQQBtuVtdHxcKeMQjPWOB83UOvFpij2b/tzbMCLp6Og4RGMpOpOGZAAgVgi5yM
	1akKZFqJ8MvqZHLG7plnSn0i7eUeMTJ+1iRL0=
Received: by 10.181.14.2 with SMTP id r2mr3858169bki.74.1219847198285;
	Wed, 27 Aug 2008 07:26:38 -0700 (PDT)
Received: by 10.210.130.1 with HTTP; Wed, 27 Aug 2008 07:26:37 -0700 (PDT)
Message-ID: <e373d31e0808270726x2deb251an5d875ebbadc6149f@mail.gmail.com>
Date: Wed, 27 Aug 2008 22:26:37 +0800
From: "Phoenix Kiula" <phoenix.kiula@gmail.com>
To: "Bill Moran" <wmoran@collaborativefusion.com>
Subject: Re: Dumping/Restoring with constraints?
Cc: "PG-General Mailing List" <pgsql-general@postgresql.org>
In-Reply-To: <20080827102403.dc69c802.wmoran@collaborativefusion.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <e373d31e0808270619uba31c8eodc2c85662b85140a@mail.gmail.com>
	<22708.1219845242@sss.pgh.pa.us>
	<e373d31e0808270712n7c599a82sca5a6bbf6cc5c20a@mail.gmail.com>
	<20080827102403.dc69c802.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/949
X-Sequence-Number: 136779

Thanks Bill for this recommendation:


> *) In the early step dump the data only with pg_dumpall --disable-triggers -a


Dumb question. Will this kind of pg_dumpall lead to downtime, I mean
is there a database lock during this time?

Thanks!