Is it possible to get Django 1.7 migrations to work fine with multiple db's?

Question

PostgreSQL

There is an application. There are two databases - one shared, which should be replicated to other servers, and one local.
In local there should be while only one table.
How to force replications to work normally? All is well with the selections. And here are the replications.
Is it possible to indicate that this particular table is not to be searched in the main db, and in the second it is not necessary to create the entire table structure?

Answer 1

I understand correctly that there are two databases: in one one table, in the other the rest?
Even if I misunderstood something, I'm sure the Database router will help you figure out which model belongs to which database. https://docs.djangoproject.com/en/1.7/topics/db/mu...
In general, I think that it is necessary to work with replications not in Django, but in the database. For samples, as I wrote above, use a router.