We have determined that we will have to shutdown slony in order to add 
tables to our databases.  This is because we have code that stops all 
triggers from firing, thus we've had to set our Slony triggers to 
'enable always'.

That being said, would it be possible to add a table to our master 
database while slony is active without causing problems to our replication?

Further, would it then be possible to add the changes to our slave at a 
later time and permit slony to properly 'catch up' on that table, while 
simply picking up where it left off on the others?

The reason for this effort is that we are in need to add a table to our 
master ASAP, but don't have the opportunity to take the downtime in 
order to properly make the changes to the slave as well.

-- 
Until later, Geoffrey

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