> The one "grand challenge" you'll face is that getting the subscription
> going, with 224GB of data, will take quite a while, which will leave
> transactions open for quite a while.

It helps if you subscribe one table at a time and merge them into an
existing set.

So, Create set, add table to set, wait..., merge set.  Repeat for each
table.

This makes the largest transaction time the largest table, rather than
the time it takes to copy everything across.


In fact, is there a reason that Slony doesn't do this by default?  Just
change ADD TABLE to spit out the 3 step process in all circumstances
using a set of temporary set IDs (sequence that wraps between 2^31 and
2^32 or something).

--