Tue May 5 12:09:41 PDT 2009
- Previous message: [Slony1-general] replication reindexing forever after initial copy
- Next message: [Slony1-general] Setting up slony 2.01 on Win2003 Server
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Christopher Browne wrote: > Joseph S <jks at selectacast.net> writes: >> What is going on here? This reindexing has been going on for far >> longer than the initial copy time. Any why is it reindexing? >> finishTableAfterCopy() should be a noop. > > finishTableAfterCopy is definitely NOT a no-op - it does indeed I guess I was confused. I grepped the slony source and found a finishTableAfterCopy() in tools/slony1_dump.sh that was a noop and assumed that was what slony was using.
- Previous message: [Slony1-general] replication reindexing forever after initial copy
- Next message: [Slony1-general] Setting up slony 2.01 on Win2003 Server
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list