shua Tolley wrote:
> From: Joshua Tolley
> Subject: Re: [GENERAL] replication from multiple "master" servers to a single
> read-only slave
> To: "Omar Mehmood"
> Cc: "Ben Chobot" , pgsql-general@postgresql.org
> Date: Tuesday, January 12, 2010, 2
On Mon, Jan 11, 2010 at 04:18:30PM -0800, Omar Mehmood wrote:
> (but I want to avoid using DB triggers).
> I will check out Bucardo.
Bucardo uses triggers just like Slony does. That said, it seems strange that
you'd want to avoid them. Is there any particular reason you want to avoid
them?
Buc
Omar Mehmood writes:
> I really don't want to use separate schemas for each master to
> logically partition the data. I ensure that the data on each master
> will not clash with each other (in terms of any DB level contraints
> such as PK), so I'd much prefer they all reside in a single schema.
>
Omar Mehmood wrote:
> Would it be possible to use PostgreSQL PITR feature to support this
> functionality ? All of the data created/updated/deleted per server
> is unique to that server, so replaying the log to the slave should
> technically be safe and the replaying logs from multiple servers
> s
n the situation where the
slave will start to increasingly lag behind over time (depends on the number of
master servers and amount of data).
I will check out Bucardo.
Omar
--- On Mon, 1/11/10, Ben Chobot wrote:
> From: Ben Chobot
> Subject: Re: [GENERAL] replication from multiple "m
On Mon, Jan 11, 2010 at 03:02:18PM -0800, Omar Mehmood wrote:
> I'm wondering if it's possible to have a setup with multiple
> "master" servers replicating to a single slave. I can guarantee
> that each server will generate unique PK values for all tables and
> all the data is partitioned (logical
I'm wondering if it's possible to have a setup with multiple "master" servers
replicating to a single slave. I can guarantee that each server will generate
unique PK values for all tables and all the data is partitioned (logically by
server) across the servers. I would simply like to have a re
