Hi,
 Thanks for the info.
 But am I supposed to only see "remoteListenThread: queue event 1,400 SYNC"
(and the event keeps growing) while its replicating or isn't there supposed
to be another log info from the remoteWorkerThread showing that its still
copying?
  And on the slave node, there is no record of "ENABLE_SUBSCRIPTION" in the
sl_event table and if I use a "WAIT FOR EVENT" command with timeout=0, it
waits endlessly. Is the slave suppose to confirm after replication or before
copying begins?
  
  Victor


"Stéphane A. Schildknecht" wrote:
> 
> Hi,
> 
> When you add a table to replication, first operation is to synchronize
> data.
> The only way Slony can do it is to delete (or truncate when possible) all
> data
> on the target table (slave) and copy all data from the source (master).
> 
> Therefore, if you table contains many Gb of data, and the net link is
> leak, it
> certainly can take a very long time.
> 
> What's more, if any error occurs while synchronizing data set for the
> first
> time, all synchronized data are lost, and the whole synchronisation
> processus
> has to be processed again.
> 
> When the first synchronisation is OK, then only the diff is transfered
> from
> master to slave.
> 
> Regards,
> 
> -- 
> Stéphane SCHILDKNECHT
> Président de PostgreSQLFr
> Tél. 09 53 69 97 12
> http://www.postgresqlfr.org
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
> 
> 

-- 
View this message in context: http://www.nabble.com/Subscribe-set-problem-tp15823349p15824694.html
Sent from the Slony-I -- General mailing list archive at Nabble.com.