<p dir="ltr">If you use the --no-table-lock flag from the contrib stuff, you can alleviate that...<br /><div
class="cm_quote"style=" color: #787878">On Fri, Apr 03, 2015 at 3:27 PM, Scott Ribe <<a
href="mailto:scott_ribe@elevated-dev.com">scott_ribe@elevated-dev.com</a>>wrote:</div><br /><div id="oldcontent"
style="background-color:rgb(255, 255, 255); background-position: initial initial; background-repeat: initial
initial;"><blockquotestyle=""><p dir="ltr">On Apr 3, 2015, at 9:59 AM, John Scalia <jayknowsunix@gmail.com>
wrote:<br /> > <br /> > So the lock should only be during this move, or does it lock the table for the entirety?
<br/><br /> The entirety. It doesn't know how to track changes that occur during the copying to the new table and apply
themafter, so it locks it the whole time. (Just went through this myself...) <br /><br /> -- <br /> Scott Ribe <br />
scott_ribe@elevated-dev.com<br /> http://www.elevated-dev.com/ <br /> https://www.linkedin.com/in/scottribe/ <br />
(303)722-0567 voice <br /><br /><br /><br /><br /><br /><br /><br /> -- <br /> Sent via pgsql-admin mailing list
(pgsql-admin@postgresql.org)<br /> To make changes to your subscription: <br />
http://www.postgresql.org/mailpref/pgsql-admin<br /></blockquote></div>
