Re: Dev chat reminder, issue 0fbcd3ab-0ace-4e23-9100-53e04aaea892

Hallo Robert Kaye:
> 
> On Jun 2, 2014, at 4:44 PM, Wieland Hoffmann <[email protected]> wrote:
> 
> > Last week I did a bit of code cleanup and then began working on
> > generating triggers to push information about changes in the DB to
> > RabbitMQ.
> 
> Cool -- could we make it so that a remote DB can consume data from
> this queue to create a very-low-latency replicated instance of MB?

I don't think so, unfortunately. The way it works (or is supposed to
work when I'm finished :P) is that once a change happens the messages
sent via RabbitMQ include only the IDs of entitities that need to be
reindexed (say you change the status of a release, you need to reindex
at least all related recordings and the release group).

It could probably be modified to just dump the changes, but that sounds
a lot like PGs streaming replication feature [0].

[0] https://wiki.postgresql.org/wiki/Streaming_Replication

-- 
Wieland