Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M43763=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1Ye8Fa-0005vO-Pm
 for pgsql-admin@arkaria.postgresql.org; Fri, 03 Apr 2015 20:31:34 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M43763=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1Ye8Fa-0002bb-85
 for pgsql-admin@arkaria.postgresql.org; Fri, 03 Apr 2015 20:31:34 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
 by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <scott@journyx.com>) id 1Ye8FZ-0002bT-CZ
 for pgsql-admin@postgresql.org; Fri, 03 Apr 2015 20:31:33 +0000
Received: from mail.journyx.com ([209.163.206.41] helo=mail.int.journyx.com)
 by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <scott@journyx.com>) id 1Ye8FV-0001mQ-VM
 for pgsql-admin@postgresql.org; Fri, 03 Apr 2015 20:31:31 +0000
Received: from localhost (localhost [127.0.0.1])
 by mail.int.journyx.com (Postfix) with ESMTP id 4EAE23000D5;
 Fri,  3 Apr 2015 15:31:28 -0500 (CDT)
Received: from mail.int.journyx.com ([127.0.0.1])
 by localhost (mail.int.journyx.com [127.0.0.1]) (amavisd-new, port 10032)
 with ESMTP id koIoGJGyZZ_S; Fri,  3 Apr 2015 15:31:28 -0500 (CDT)
Received: from localhost (localhost [127.0.0.1])
 by mail.int.journyx.com (Postfix) with ESMTP id 209F73000D8;
 Fri,  3 Apr 2015 15:31:28 -0500 (CDT)
X-Amavis-Modified: Mail body modified (using disclaimer) -
 mail.int.journyx.com
X-Virus-Scanned: amavisd-new at mail.int.journyx.com
Received: from mail.int.journyx.com ([127.0.0.1])
 by localhost (mail.int.journyx.com [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id EZuiyNCK1NwX; Fri,  3 Apr 2015 15:31:27 -0500 (CDT)
Received: from mail.int.journyx.com (zimbra.int.journyx.com [192.168.100.5])
 by mail.int.journyx.com (Postfix) with ESMTP id DD4203000D5;
 Fri,  3 Apr 2015 15:31:27 -0500 (CDT)
MIME-Version: 1.0
X-Mailer: CloudMagic
X-Mailer: Zimbra 8.6.0_GA_1153 (MobileSync - CloudMagic)
X-Cm-Message-Id: 
 1428093087249046a61ef9b629534f7e83d4498bea88e4f0551ef89f3cd86376949502
In-Reply-To: <93CAB446-41FF-4032-935D-CBABFF233906@elevated-dev.com>
References: <551EB8D4.7050406@gmail.com>
To: "Scott Ribe" <scott_ribe@elevated-dev.com>
Cc: "John Scalia" <jayknowsunix@gmail.com>, pgsql-admin@postgresql.org
Subject: Re: vacuum and table locking
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-ID: 
 <935009944.851005.1428093087652.JavaMail.zimbra@zimbra.int.journyx.com>
From: Scott Whitney <scott@journyx.com>
Date: Fri, 3 Apr 2015 15:31:27 -0500 (CDT)
Thread-Topic: vacuum and table locking
Thread-Index: vV+AWq+6eracmuOYqBCir83MZhlXCw==
X-Pg-Spam-Score: -0.8 (/)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

<p dir=3D=22ltr=22>If you use the --no-table-lock flag from the contrib =
stuff, you can alleviate that...</p>
<br/><div class=3D=22cm=5Fquote=22 style=3D=22 color: #787878=22>On Fri, =
Apr 03, 2015 at 3:27 PM, Scott Ribe &lt;<a href=3D=22mailto:scott=5Fribe@el=
evated-dev.com=22>scott=5Fribe@elevated-dev.com</a>&gt; =
wrote:</div><br><div id=3D=22oldcontent=22 style=3D=22background-color: =
rgb(255, 255, 255); background-position: initial initial; =
background-repeat: initial initial;=22><blockquote style=3D=22=22><p =
dir=3D=22ltr=22>On Apr 3, 2015, at 9:59 AM, John Scalia =
&lt;jayknowsunix@gmail.com&gt; wrote:
<br>
&gt;=20
<br>
&gt; So the lock should only be during this move, or does it lock the table=
 for the entirety=3F
<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>
--=20
<br>
Scott Ribe
<br>
scott=5Fribe@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>
--=20
<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>