I spent yesterday getting my 7.4.2 database replication up and running.
33 tables and 15 sequences....all being replicated from my master 
(production) system to my slave (backup).
Very impressed with how painless it was (used the FreeBSD port for 
installation).
I'll spend the rest of the week benchmarking to see what kind of impact 
it will have on my cpu/network/io.

Some questions I have don't seem to be covered in the (so far) limited 
documentation.  Laziness prevents me from looking at the source and 
stored procedures so I present my questions here:

1.  How do I stop the sync 'gracefully'?  So far I've been kill -9ing 
the slon daemon process on master or slave to halt it.  That can't be 
right. 
2.  Logging.  I notice that the slon daemon has a -d (debug level)...but 
where does slony logging end up? 
3.  Vacuuming.  Does it have any effect on the replication process?  I 
assume that the 'slave' database will end up needing vacuuming just as 
often as the master, so will the 'denyaccess()' function call that's 
attached to every add/update/delete in my slave database prevent me from 
vacuuming it?  Should I halt replicate before vacuuming?
4.  If I lose my master database, and want to move my backup box/db into 
production, wont the dennyaccess() triggers placed on the database 
prevent me from 'functioning' properly?



great product.....
Thanks in advance for the help.


jamiel at istreamimaging.com