Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id BC2279FB463 for ; Sun, 29 Oct 2006 13:14:42 -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 05546-10 for ; Sun, 29 Oct 2006 17:14:35 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from heaven.kostyrka.org (h1634.serverkompetenz.net [81.169.154.44]) by postgresql.org (Postfix) with ESMTP id 5B0939FB413 for ; Sun, 29 Oct 2006 13:10:44 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by heaven.kostyrka.org (Postfix) with ESMTP id BD1834FB8E; Sun, 29 Oct 2006 18:10:42 +0100 (CET) Received: from heaven.kostyrka.org ([127.0.0.1]) by localhost (heaven.kostyrka.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19716-02; Sun, 29 Oct 2006 18:10:42 +0100 (CET) Received: from [192.168.1.9] (85-124-82-106.dynamic.xdsl-line.inode.at [85.124.82.106]) by heaven.kostyrka.org (Postfix) with ESMTP id 69DF24FB84; Sun, 29 Oct 2006 18:10:42 +0100 (CET) Subject: Re: VACUUMs take twice as long across all nodes From: Andreas Kostyrka To: Andrew Sullivan Cc: pgsql-performance@postgresql.org In-Reply-To: <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> <20061029164319.GG14585@phlogiston.dyndns.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-0drm0RJn6kaGkBnwUhe/" Date: Sun, 29 Oct 2006 18:12:09 +0100 Message-Id: <1162141929.7606.4.camel@andi-lap> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 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/605 X-Sequence-Number: 21734 --=-0drm0RJn6kaGkBnwUhe/ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Am Sonntag, den 29.10.2006, 11:43 -0500 schrieb Andrew Sullivan: > 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" an= d > > "constraints". Do get a restorable backup you need to put the table > > definitions stuff before your data, and the constraints after the data > > copy. >=20 > This will work, yes, but you don't get a real point-in-time dump this But one does, because one can dump all data in one pg_dump call. And with slony enabled, schema changes won't happen by mistake, they tend to be a thing for the Slony High Priest, nothing for mere developers ;) Andreas --=-0drm0RJn6kaGkBnwUhe/ Content-Type: application/pgp-signature; name=signature.asc Content-Description: Dies ist ein digital signierter Nachrichtenteil -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBFRODpHJdudm4KnO0RAgyNAKCCX9yex7F3EWSUS2T8/MPRgK0h0wCdE8m9 MnZPhN2gEBKNpABfPrqcNng= =jw12 -----END PGP SIGNATURE----- --=-0drm0RJn6kaGkBnwUhe/--