Good morning all,

I seem to recall (I think it was touched on by someone else) that this
aspect *might* be addressed in a near-future version of slony:

Given that some users of slony have large (your definition of large will
vary, but let's say DBs in excess of 100GB) databases, and that the
initial replication of a DB can take weeks, would it not be a great idea
to have a more efficient initial 'copy' mode?  ie, either allow a user to
dump/restore to all slaves, then start replication from that point
(without truncating/copying/etc), or, build this functionality into slony
so it does the dump/restore, but does not then truncate all tables and
start from scratch?

For smaller DBs this doesn't present a problem, but for larger DDs coupled
with LARGE clusters, this is a major problem.

Regards
Henry