At 23:21 20/11/2007, Robert Landrum wrote:
I'm working with a very large database. 300 tables and about 350
sequences. Dumped, it's about 8GB of data.
I've read several posts that seem to indicate that I need to let
slony sync my data between the master and the slave when I subscribe
the slave to the master. I would prefer to avoid this, as it'll
take quite a while for the sync to take place. After about 2 hours
and 30 minutes, I'm only about 5% complete.
Well, I don't quite understand how you could have a replication
without syncing the data? Also, we have several large databases
replicated including one where the (compressed) dump is 8GB as well,
and it certainly didn't take 2 days to do the initial sync. Are you
using the last versions of postgresql and slony? Is your slave
correctly configured (both hardware- and software-wise)? Did you
check that there are no errors during the replication which would
cause slony to abort and restart again and again?
Is this just a limitation of slony? Or is there a workaround I've missed?
What other option would you imagine there could be?
Jacques.
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
