Han He wrote:
> Thanks for your kind reply.
> Actually what I mean 'atomic' is that, for example, if on parent, 
> update table A and table B, then slony trigger replication on slave 
> node, update table A succeed, however update table B fail, can slony 
> rollback the table A?  
Actually, there's a stronger condition than that...

If the update to table B fails on the subscriber, Slony-I will roll the 
whole set of changes back, and is unable to NOT rollback the update to 
table A.