Re: replication with table add/removes..

How can I make them constantly create restore points? Once I create
recover.conf it creates recover.done but what about those new queries
that comes after that? Do I have to re-create recover.conf? Or how do I
achive constant logging to slaves? This issue is not clear in the
documentation http://www.postgresql.org/docs/8.3/interactive/continuous-archiving.html

----- Original Message ----
From: Chris Browne <cbbrowne(at)acm(dot)org>
To: pgsql-admin(at)postgresql(dot)org
Sent: Wednesday, October 8, 2008 7:47:45 PM
Subject: Re: [ADMIN] replication with table add/removes..

martinbadie(at)yahoo(dot)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