Re: DBLink - Mailing list pgsql-admin

From Bèrto ëd Sèra
Subject Re: DBLink
Date
Msg-id CAKwGa__xSsq=htW984s3svAMftMgYgRnxEAQqffxZNUzwFYBEQ@mail.gmail.com
Whole thread Raw
In response to Re: DBLink  (Rob Richardson <RDRichardson@rad-con.com>)
List pgsql-admin
No. Here it's the master pushing change to the slave, rather than the slave pulling it (as you'd normally expect), hence the inner fragility of the model. Moreover, replication is about having "exactly the same thing" in two places, while this could be an audit log he keeps in its historical completeness on a remote box, while pruning the local table on regular basis, so not exactly a replication. 

Bèrto

On 25 April 2013 16:17, Rob Richardson <RDRichardson@rad-con.com> wrote:
Isn't that basically what replication is supposed to do?

RobR, quite possibly revealing his ignorance about replication.


--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



--
==============================
If Pac-Man had affected us as kids, we'd all be running around in a darkened room munching pills and listening to repetitive music.

pgsql-admin by date:

Previous
From: Rob Richardson
Date:
Subject: Re: DBLink
Next
From: Tom Lane
Date:
Subject: Re: Simultaneous index creates on different schemas cause deadlock?