Fri Jun 15 05:20:21 PDT 2012
- Previous message: [Slony1-general] How to fast the Slave Sync with Primary on large tables ?
- Next message: [Slony1-general] Slony configuration
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thank you Steve for the reply. > > Someone asked a similar question a few days ago, my comments > http://lists.slony.info/**pipermail/slony1-general/2012-**June/012217.html<http://lists.slony.info/pipermail/slony1-general/2012-June/012217.html>mostly apply to you as well. > > Yep, almost similar. > The Slony initial COPY SET needs to copy the entire contents of the table. > This will be no faster than the time it would take to perform a pg_dump. > Normal rules for speed up bulk loads with postgresql apply. Are you IO > bound, CPU bound or network bound? > > So, COPY SET is similar the count of pg_dump time. Ok. Got it. > The sync_interval and sync_interval_timeout only come into play AFTER the > initial copy_set is done (I think). > > Ok. I have another question for which I will be starting another thread after this reply. --Raghav -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20120615/2aead120/attachment.htm
- Previous message: [Slony1-general] How to fast the Slave Sync with Primary on large tables ?
- Next message: [Slony1-general] Slony configuration
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list