Well, I'm not getting any bites on this issue, so either I'm the first
person to try this, or I have bad breath.. ;)
Quick question. Is the slony_tools.conf file only used at
initialization and startup of the slony processes? That is, once I've
got my replication up and running, is the slony_tools.conf file
referenced again? The point is, I'm thinking that I can create multiple
slony_tools.conf files, one for each database. Link the appropriate one
during the startup of slony for that database, then move on to the next
database once that replication is going for the first one.
It appears to me that the slony_tools.conf file is simply a perl module
that must be referenced by the code, so I'm assuming I can make this
work, I just don't want to be hacking a bunch of different scripts.
--
Until later, Geoffrey
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
- Benjamin Franklin
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
