Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 18817B5DBC4 for ; Mon, 15 Aug 2011 19:50:33 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 43967-03 for ; Mon, 15 Aug 2011 22:50:26 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from acidenitrix.villemain.org (acidenitrix.villemain.org [91.121.90.165]) by mail.postgresql.org (Postfix) with ESMTP id 14F15B5DBBE for ; Mon, 15 Aug 2011 19:50:25 -0300 (ADT) Received: from [89.157.192.174] (helo=DimIMac.local) by acidenitrix.villemain.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1Qt5zE-0001XJ-HA; Tue, 16 Aug 2011 00:50:24 +0200 Received: by DimIMac.local (Postfix, from userid 501) id 695A126B7677; Tue, 16 Aug 2011 00:50:18 +0200 (CEST) From: Dimitri Fontaine To: Craig James Cc: pgsql-admin@postgresql.org Subject: Re: Postgresql 8.4 replication using Londiste Organization: 2ndQuadrant References: <4DEFD00C.8030600@nasa.gov> <4DEFDB81.8060003@emolecules.com> User-Mail-Address: dimitri@2ndQuadrant.fr Date: Tue, 16 Aug 2011 00:50:18 +0200 In-Reply-To: <4DEFDB81.8060003@emolecules.com> (Craig James's message of "Wed, 08 Jun 2011 13:28:49 -0700") Message-ID: User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (darwin) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.18 tagged_above=-10 required=5 tests=BAYES_00=-1.9, SARE_SPEC_REPLICA=0.72 X-Spam-Level: X-Archive-Number: 201108/138 X-Sequence-Number: 38125 Craig James writes: > On the other hand, I've noticed that Londiste doesn't know when you chang= e a > table. You might be able to create your one-column table (plus PK), start > replication with Londiste, then do ALTER TABLE to add the rest of the > columns. A hack for sure. And it stopped working somewhere in the 2.1 branch, I would guess by 2.1.9 from memory. Now the trigger notices when you ALTER TABLE and will queue events with the new columns by itself. Well, that might also depend on which trigger you use, but the default one is now smart enough. Skytools3 ahead!=C2=A0:) Regards, --=20 Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support