On Thu, Jan 10, 2013 at 11:22 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> EnterpriseDB reports that our documentation states that ALTER TABLE
> takes SHARE UPDATE EXCLUSIVE and ACCESS EXCLUSIVE lock modes. However,
> their testing shows only ACCESS EXCLUSIVE locks. Is this accurate?
> Have we changed how ALTER TABLE locks but didn't update our docs?
By looking at AlterTableGetLevelLock:tablecmds.c, you are right. All the
ALTER TABLE operations now take an AccessExclusiveLock for all the commands
since 9.1 due to issues with lower level locks involving things like
catalog using SnapshotNow.
Docs should be updated in consequence.
The 9.1-prior locks can be reenabled by using the flag
Perhaps this could also be specified in the docs.
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2013-01-10 03:27:54|
|Subject: Re: Lock levels for ALTER TABLE|
|Previous:||From: Noah Misch||Date: 2013-01-10 03:11:36|
|Subject: Re: lazy_vacuum_heap()'s removal of HEAPTUPLE_DEAD tuples|