Re: vacuum and table locking

From: Scott Whitney <scott(at)journyx(dot)com>
To: "Scott Ribe" <scott_ribe(at)elevated-dev(dot)com>
Cc: "John Scalia" <jayknowsunix(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: vacuum and table locking
Date: 2015-04-03 20:31:27
Message-ID: 935009944.851005.1428093087652.JavaMail.zimbra@zimbra.int.journyx.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

<p dir="ltr">If you use the --no-table-lock flag from the contrib stuff, you can alleviate that...</p>
<br/><div class="cm_quote" style=" color: #787878">On Fri, Apr 03, 2015 at 3:27 PM, Scott Ribe &lt;<a href="mailto:scott_ribe(at)elevated-dev(dot)com">scott_ribe(at)elevated-dev(dot)com</a>&gt; wrote:</div><br><div id="oldcontent" style="background-color: rgb(255, 255, 255); background-position: initial initial; background-repeat: initial initial;"><blockquote style=""><p dir="ltr">On Apr 3, 2015, at 9:59 AM, John Scalia &lt;jayknowsunix(at)gmail(dot)com&gt; wrote:
<br>
&gt;
<br>
&gt; 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 them after, so it locks it the whole time. (Just went through this myself...)
<br>

<br>
--
<br>
Scott Ribe
<br>
scott_ribe(at)elevated-dev(dot)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(at)postgresql(dot)org)
<br>
To make changes to your subscription:
<br>
http://www.postgresql.org/mailpref/pgsql-admin
<br>
</p>
</blockquote></div>

Attachment Content-Type Size
unknown_filename text/html 1.2 KB

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Matheus de Oliveira 2015-04-04 12:50:46 Re: vacuum and table locking
Previous Message Scott Ribe 2015-04-03 20:25:48 Re: vacuum and table locking