From: | Bèrto ëd Sèra <berto(dot)d(dot)sera(at)gmail(dot)com> |
---|---|
To: | Rob Richardson <RDRichardson(at)rad-con(dot)com> |
Cc: | Igor Neyman <ineyman(at)perceptron(dot)com>, Thomaz Luiz Santos <thomaz(dot)santos(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: DBLink |
Date: | 2013-04-25 15:21:27 |
Message-ID: | CAKwGa__xSsq=htW984s3svAMftMgYgRnxEAQqffxZNUzwFYBEQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)rad-con(dot)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(at)postgresql(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-04-25 17:17:31 | Re: [ADMIN] Simultaneous index creates on different schemas cause deadlock? |
Previous Message | Rob Richardson | 2013-04-25 15:17:32 | Re: DBLink |