Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id A14689FA491 for ; Sun, 29 Oct 2006 12:43:30 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 02305-02 for ; Sun, 29 Oct 2006 16:43:25 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from main2.mycybernet.net (main2.mycybernet.net [209.222.63.140]) by postgresql.org (Postfix) with ESMTP id 7B64E9FB1F8 for ; Sun, 29 Oct 2006 12:43:25 -0400 (AST) Received: from 227-54-222-209.mycybernet.net ([209.222.54.227] helo=phlogiston.dydns.org) by main2.mycybernet.net with esmtp (Exim 4.62) (envelope-from ) id 1GeDkI-0006bG-WF for pgsql-performance@postgresql.org; Sun, 29 Oct 2006 11:42:51 -0500 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id 450D54172; Sun, 29 Oct 2006 11:43:19 -0500 (EST) Date: Sun, 29 Oct 2006 11:43:19 -0500 From: Andrew Sullivan To: pgsql-performance@postgresql.org Subject: Re: VACUUMs take twice as long across all nodes Message-ID: <20061029164319.GG14585@phlogiston.dyndns.org> References: <20196.1161874041@sss.pgh.pa.us> <20061026160609.5e94e581.gdh@laterooms.com> <20061026191728.GD26892@nasby.net> <20061026213556.174bd7b5.gdh@laterooms.com> <20061026220937.GA6866@phlogiston.dyndns.org> <20061027102025.8183c5d9.gdh@laterooms.com> <20061029145825.GB14585@phlogiston.dyndns.org> <20061029150826.80afe324.gdh@laterooms.com> <20061029153404.GF14585@phlogiston.dyndns.org> <1162139073.7606.1.camel@andi-lap> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1162139073.7606.1.camel@andi-lap> User-Agent: Mutt/1.5.9i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200610/604 X-Sequence-Number: 21733 On Sun, Oct 29, 2006 at 05:24:33PM +0100, Andreas Kostyrka wrote: > Actually, you need to get the schema from the master node, and can take > the data from a slave. In mixing dumps like that, you must realize that > there are two seperate parts in the schema dump: "table definitions" and > "constraints". Do get a restorable backup you need to put the table > definitions stuff before your data, and the constraints after the data > copy. This will work, yes, but you don't get a real point-in-time dump this way. (In any case, we're off the -performance charter now, so if anyone wants to pursue this, I urge you to take it to the Slony list.) A -- Andrew Sullivan | ajs@crankycanuck.ca Windows is a platform without soap, where rats run around in open sewers. --Daniel Eran