Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Ye8AF-0005hU-Jx for pgsql-admin@arkaria.postgresql.org; Fri, 03 Apr 2015 20:26:03 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Ye8AE-0000Sf-8R for pgsql-admin@arkaria.postgresql.org; Fri, 03 Apr 2015 20:26:02 +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 ) id 1Ye8AC-0000ST-5e for pgsql-admin@postgresql.org; Fri, 03 Apr 2015 20:26:00 +0000 Received: from mailout.easymail.ca ([64.68.201.169]) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1Ye8A4-0001gj-8n for pgsql-admin@postgresql.org; Fri, 03 Apr 2015 20:25:58 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 798CFE099; Fri, 3 Apr 2015 16:25:50 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at mailout.easymail.ca X-Spam-Flag: NO X-Spam-Score: -3.824 X-Spam-Level: X-Spam-Status: No, score=-3.824 required=5 tests=[ALL_TRUSTED=-1.8, AWL=-0.117, BAYES_00=-2.599, DNS_FROM_AHBL_RHSBL=0.692] Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (easymail-mailout.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id spvxkn4Z-fa6; Fri, 3 Apr 2015 16:25:50 -0400 (EDT) Received: from [192.168.0.15] (c-76-120-51-139.hsd1.co.comcast.net [76.120.51.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 09B51E093; Fri, 3 Apr 2015 16:25:49 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: vacuum and table locking From: Scott Ribe In-Reply-To: <551EB8D4.7050406@gmail.com> Date: Fri, 3 Apr 2015 14:25:48 -0600 Cc: "pgsql-admin@postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: <93CAB446-41FF-4032-935D-CBABFF233906@elevated-dev.com> References: <551EB8D4.7050406@gmail.com> To: John Scalia X-Mailer: Apple Mail (2.2070.6) X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On Apr 3, 2015, at 9:59 AM, John Scalia wrote: >=20 > So the lock should only be during this move, or does it lock the table fo= r the entirety? The entirety. It doesn't know how to track changes that occur during the co= pying to the new table and apply them after, so it locks it the whole time.= (Just went through this myself...) --=20 Scott Ribe scott_ribe@elevated-dev.com http://www.elevated-dev.com/ https://www.linkedin.com/in/scottribe/ (303) 722-0567 voice --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin