pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Scott Whitney <scott@journyx.com>
To: Scott Ribe <scott_ribe@elevated-dev.com>
Cc: John Scalia <jayknowsunix@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: vacuum and table locking
Date: Fri, 3 Apr 2015 15:31:27 -0500 (CDT)
Message-ID: <935009944.851005.1428093087652.JavaMail.zimbra@zimbra.int.journyx.com> (raw)
In-Reply-To: <93CAB446-41FF-4032-935D-CBABFF233906@elevated-dev.com>
References: <551EB8D4.7050406@gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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@elevated-dev.com">scott_ribe@elevated-dev.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@gmail.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@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>
</p>
</blockquote></div>




view thread (8+ messages)  latest in thread

Message-ID: <935009944.851005.1428093087652.JavaMail.zimbra@zimbra.int.journyx.com>
Permalink:  ../935009944.851005.1428093087652.JavaMail.zimbra@zimbra.int.journyx.com/
Also on:    postgresql.org/message-id/935009944.851005.1428093087652.JavaMail.zimbra@zimbra.int.journyx.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: scott@journyx.com, scott_ribe@elevated-dev.com, jayknowsunix@gmail.com
  Subject: Re: vacuum and table locking
  In-Reply-To: <935009944.851005.1428093087652.JavaMail.zimbra@zimbra.int.journyx.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox