> Hello, > > I have a few questions concerning Slony: > > 1. To my understanding each database that is to be replicated has to > have their own slon process running. Is this correct? It seems crazy to > me that for example 10 databases you should have 10 different slon > processes.
If there were only one process, then you'd be in big trouble if you were trying to replicate to three sites across two WAN connections. Ten processes for ten replicas in what is a peer-to-peer communications system is entirely reasonable. > 2. Is it possible to have a table created to a replicated database to be > automatically added to the replication set? No, a table can NEVER be added to an active, replicating replication set. Further, as there is no way to add triggers to system tables, there is no way to have a "hook" to allow the replication system to automatically detect the introduction of new tables. The applicable dogma is that competent system designers don't simply throw new tables at their systems; adding tables to a system normally represents an upgrade process which requires some systematic process for its application. Slony-I provides a systematic way (EXECUTE SCRIPT) to assist in the application of upgrades, which may be needed along with the creation of new replication sets to add in new replicable objects. There are things about this that are somewhat painful. It's possible that further automation could be applied to some of this. But at this point, it is what it is... _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
