I probably should have posted this a long while ago.  We are in the 
process of setting up a single slony slave for the sake of disaster 
recovery.  Our set up is relatively complex, and I thought I'd throw out 
some questions regarding it, in the hope that anyone here on the list 
might point out issues that may stop us from completing this process 
successfully.  My apologies for the length of this post in advance.

Our current production setup has two boxes that share a data silo.  A 
hot-hot scenario where roughly half the postmasters run from one 
machine, the other half from the other.  In the event of one machine 
failure, the live box picks up all the databases.

We are running Red Hat Advance Server 4, postgresql 7.4.18.

Our plan is to replicate all existing databases to another box, for the 
short term, it will reside in the same location as the master boxes. 
Long term, it will be moved to a data center in Nashville, TN, we are in 
Gainesville GA.

We currently have 9 postmasters running on one machine, 8 on the other. 
  This number will likely grow.

My plan is to 'turn on' slony for each database one at a time, in order 
to reduce the initial hit on the servers as slony performs the initial 
replication of the data in each database. The existing databases' 
directories range from 407M to 8.5G, most of which are in the 1.5G range.

The majority of the databases have identical schemas.  Will I be 
configuring separate instances of slony per database, or will a single 
instance handle multiple databases?

Thanks for any assistance and feedback on this scenario.

-- 
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin