On Friday 21 December 2007 04:39:27 Geoffrey wrote:
> 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.

slon_tools.conf is uses everytime you use one of the helper scripts to manage 
your replication, weather this is to to perform DDL, failover, switchover, 
add a node or remove a node (and more).



>
> 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.

All of the tools if I'm not mistaken have the ability to be passed a config 
file, so there should be no hacking required.  except on those tools which 
can;t be passed a config file.




-- 
Darcy Buskermolen
Command Prompt, Inc.
+1.503.667.4564 X 102
http://www.commandprompt.com/
PostgreSQL solutions since 1997