Ben Chobot wrote:
> On Mar 22, 2010, at 7:10 PM, Steve Singer wrote:


> Right, if we make the origins on different nodes, that's clearly asking for problems. But if we keep all set origins to be on the same node? I understand slony doesn't enforce that, but assuming I don't try so hard to shoot my foot, might I referential integrity problems? 
> 

Tables in all sets that flow from a particular provider to a particular 
subscriber are sent at the same time, so I can't think of any integrity 
issues that you'll have if you keep all of the sets originating on the 
same node.

>> When does something cross the line from being unmanageable to unworkable? Rather than debating that point you are probably better off spending time trying to find a way to do what you want without having foreign keys that cross set boundaries.
> 
> Any suggestions on a better way to go about it? 


-- 
Steve Singer
Afilias Canada
Data Services Developer
416-673-1142