From: Scott Ribe <scott_ribe@elevated-dev.com>
To: John Scalia <jayknowsunix@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: vacuum and table locking
Date: Fri, 3 Apr 2015 14:25:48 -0600
Message-ID: <93CAB446-41FF-4032-935D-CBABFF233906@elevated-dev.com> (raw)
In-Reply-To: <551EB8D4.7050406@gmail.com>
References: <551EB8D4.7050406@gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On Apr 3, 2015, at 9:59 AM, John Scalia <jayknowsunix@gmail.com> wrote:
>
> So the lock should only be during this move, or does it lock the table for the entirety?
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...)
--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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_ribe@elevated-dev.com, jayknowsunix@gmail.com
Subject: Re: vacuum and table locking
In-Reply-To: <93CAB446-41FF-4032-935D-CBABFF233906@elevated-dev.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