Tory M Blue tmblue at gmail.com
Thu Feb 13 14:15:18 PST 2014
I had some hints given to me in the past, but no real understanding to how
it would be achieved so asking again.

I'm turning up a DR site and my past tests have failed due to some network
timeout, since the index creation of some of the tables would take a long
time, and thus no packets were being exchanged between the master and the
slave and the connection was being reaped.

so I'm wondering how do I change my scripts to create the index's at the
end? I obviously can't drop the index on the master or everything will go
to heck in a hand basket, but is there an instruction set when I'm adding a
node and adding sets to that node, to tell it to ignore the indexes?


 SLONIK_COMMANDS="$SLONIK_COMMANDS
     subscribe set ( id = 1, provider = $SLAVE_NODE, receiver =
$ADDNODE_ID, forward = yes);
     subscribe set ( id = 2, provider = $SLAVE_NODE, receiver =
$ADDNODE_ID, forward = yes);
     subscribe set ( id = 3, provider = $SLAVE_NODE, receiver =
$ADDNODE_ID, forward = yes);
 "

Wondering where or how I could make changes to allow the copies to just
continue non stop for all the tables and then again to create the index on
the backend of the replication?

Thanks
Tory
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20140213/5f4d8f31/attachment.htm 


More information about the Slony1-general mailing list