Обсуждение: replication with table add/removes..

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

On Wed, Oct 8, 2008 at 9:10 AM, Martin Badie <martinbadie@yahoo.com> wrote:
> 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.

I think that pgpool might work for this.  There are probably some
other "front end" type replication systems that would work too.