Hey guys,

I have a database I'm currently replicating with slony. Most tables are in the same set. I've recently been given the requirement that a few of my tables need to be replicated to an additional slave. I'm new to Slony, but I believe this means I'll need to create a new set, subscribe the current slave and the new, lesser slave to that new set, and then move those tables into the new set. Is that correct?

If so, then I have a concern with the minimum amount of tables I actually need to put into my new set. There is a very specific list of tables I want to replicate to my new slave. However, the documentation leads me to believe that I don't want foreign keys to cross set boundaries, and that means I would need to put more tables into my new set than I wish. Can somebody explain why foreign keys crossing sets is bad? I *think* it might be because slony might not apply updates from multiple sets in a single transaction - but if that was the case, then it seems that having foreign keys span set boundaries wouldn't merely be undesirable, but rather unworkable. So.... I must have something wrong?