Re: Replication identifiers, take 4

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: Replication identifiers, take 4
Дата
Msg-id 54E1B33D.6030204@vmware.com
обсуждение исходный текст
Ответ на Re: Replication identifiers, take 4  (Andres Freund <andres@2ndquadrant.com>)
Ответы Re: Replication identifiers, take 4  (Andres Freund <andres@2ndquadrant.com>)
Список 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




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Allow "snapshot too old" error, to prevent bloat
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Replication identifiers, take 4