Re: vacuum and table locking

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: John Scalia <jayknowsunix(at)gmail(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: vacuum and table locking
Date: 2015-04-03 20:25:48
Message-ID: 93CAB446-41FF-4032-935D-CBABFF233906@elevated-dev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Apr 3, 2015, at 9:59 AM, John Scalia <jayknowsunix(at)gmail(dot)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(at)elevated-dev(dot)com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Whitney 2015-04-03 20:31:27 Re: vacuum and table locking
Previous Message Kevin Grittner 2015-04-03 17:59:05 Re: vacuum and table locking