pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedreplication with table add/removes..
4+ messages / 3 participants
[nested] [flat]
* replication with table add/removes..
@ 2008-10-08 15:10 Martin Badie <martinbadie@yahoo.com>
0 siblings, 2 replies; 4+ messages in thread
From: Martin Badie @ 2008-10-08 15:10 UTC (permalink / raw)
To: pgsql-admin
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.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: replication with table add/removes..
@ 2008-10-08 16:47 Chris Browne <cbbrowne@acm.org>
parent: Martin Badie <martinbadie@yahoo.com>
1 sibling, 0 replies; 4+ messages in thread
From: Chris Browne @ 2008-10-08 16:47 UTC (permalink / raw)
To: pgsql-admin
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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: replication with table add/removes..
@ 2008-10-08 18:28 Scott Marlowe <scott.marlowe@gmail.com>
parent: Martin Badie <martinbadie@yahoo.com>
1 sibling, 0 replies; 4+ messages in thread
From: Scott Marlowe @ 2008-10-08 18:28 UTC (permalink / raw)
To: Martin Badie <martinbadie@yahoo.com>; +Cc: pgsql-admin
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.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: replication with table add/removes..
@ 2008-10-16 08:10 Martin Badie <martinbadie@yahoo.com>
0 siblings, 0 replies; 4+ messages in thread
From: Martin Badie @ 2008-10-16 08:10 UTC (permalink / raw)
To: pgsql-admin
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@acm.org>
To: pgsql-admin@postgresql.org
Sent: Wednesday, October 8, 2008 7:47:45 PM
Subject: Re: [ADMIN] 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
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2008-10-16 08:10 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-10-08 15:10 replication with table add/removes.. Martin Badie <martinbadie@yahoo.com>
2008-10-08 16:47 ` Chris Browne <cbbrowne@acm.org>
2008-10-08 18:28 ` Scott Marlowe <scott.marlowe@gmail.com>
2008-10-16 08:10 Re: replication with table add/removes.. Martin Badie <martinbadie@yahoo.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox