On Fri, 2004-12-31 at 10:15 -0600, Jeremiah Jahn wrote:
> Slony seems to be running a little slow, and I was wondering if there is
> a way to speed things up that I missed in the documentation.

Going back through our notes, another thing you can do to help is not
install any foreign keys for the initial copy AND split up the
structure.

That is, make one independent set for each structure and once it's
copied and caught up, send across another structure.

When doing everything as a single set, normally the sl_log structure
will rapidly fill up with data which it has significant difficulties at
the moment (Jan has a fix in mind) clearing out due to large transaction
lengths (initial copy is all one transaction, as are backups, etc.).

Doing it one table at a time prevents the sl_log structure from falling
as far behind and can take some time and serious load off the "catchup"
period.

In our case, the catchup period took longer than the initial copy.
--