| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Steve Singer <steve(at)ssinger(dot)info>, Petr Jelinek <petr(at)2ndquadrant(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Replication identifiers, take 4 |
| Date: | 2015-02-16 09:07:09 |
| Message-ID: | 54E1B33D.6030204@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/16/2015 02:21 AM, Andres Freund wrote:
> Furthermore the fact that the origin of records is recorded allows to
> avoid decoding them in logical decoding. That has both efficiency
> advantages (we can do so before they are stored in memory/disk) and
> functionality advantages. Imagine using a logical replication solution
> to replicate inserts to a single table between two databases where
> inserts are allowed on both - unless you prevent the replicated inserts
> from being replicated again you obviously have a loop. This
> infrastructure lets you avoid that.
That makes sense.
How does this work if you have multiple replication systems in use in
the same cluster? You might use Slony to replication one table to one
system, and BDR to replication another table with another system. Or the
same replication software, but different hosts.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-02-16 09:18:39 | Re: Replication identifiers, take 4 |
| Previous Message | Andres Freund | 2015-02-16 08:41:59 | Re: Allow "snapshot too old" error, to prevent bloat |