<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Feb 14, 2014 at 10:35 AM, Vick Khera <span dir="ltr"><<a href="mailto:vivek@khera.org" target="_blank">vivek@khera.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 13, 2014 at 5:15 PM, Tory M Blue <span dir="ltr"><<a href="mailto:tmblue@gmail.com" target="_blank">tmblue@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra">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?</div>
<div class="gmail_extra"></div></blockquote></div><br>I'm pretty sure slony disables indexes while copying, then re-builds them after it is done.</div></div>
</blockquote></div><br><br></div><div class="gmail_extra">Actually I believe this is beyond slony. The schema tells postgres what to do, so if it's creating indexes when the table is created, seems like everything pauses / waits for the index to be done, before moving on to the next table copy. <br>
<br></div><div class="gmail_extra">So I think editing the schema to do the indexes at the end or not at all (make it manual), one should be able to use that schema on a remote slon host, that host will not pause to create indexes, and allow slony to push the data without a significant pause (some of our indexes have taken 4+ hours to create).<br>
<br></div><div class="gmail_extra">I'm going to test this anyways, I don't see anything particular to slon to stop this behaviour<br><br></div><div class="gmail_extra">Thanks<br>Tory<br></div></div>