From: Chris Browne <cbbrowne@acm.org>
Subject: Re: replication with table add/removes..
Date: Wed, 08 Oct 2008 12:47:45 -0400
Organization: cbbrowne Computing Inc
Lines: 25
Message-ID: <87myhff2z2.fsf@dba2.int.libertyrms.com>
References: <103015.29150.qm@web59907.mail.ac4.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Gnus/5.110006 (No Gnus v0.6) XEmacs/21.4.21 (linux)
Cancel-Lock: sha1:rbdqpbHV+NGP3Df4orIJ5hJKJSc=
To: pgsql-admin@postgresql.org

martinbadie@yahoo.com (Martin Badie) writes:
> Hi, I have a system that have constant table adds/removes are
> present. I want to make a replication between master and slaves but
> not sure which one is the best solution for that kind of a
> situation. Since I am new to replication stuff on postgresql I am
> truly lost but I know that Slony is not an answer for replications
> where table add/remove are present.  Best Regards.

The only way that is at all supportable right now in that regard is to use PITR:
   http://www.postgresql.org/docs/8.3/interactive/continuous-archiving.html

That does NOT allow you to query the backup nodes; in order to do so,
you must activate them, which amounts to failing over to the backup
node.

If your system doesn't have a stable schema, that seems like a
problem...
-- 
select 'cbbrowne' || '@' || 'linuxfinances.info';
http://linuxdatabases.info/info/wp.html
Objects & Markets
"Object-oriented programming is about the modular separation of what
from how. Market-oriented, or agoric, programming additionally allows
the modular separation of why."
-- Mark Miller