From: Robert Haas Date: Thu, 3 Feb 2011 20:14:27 +0000 (-0500) Subject: ALTER TABLE sometimes takes only ShareUpdateExclusiveLock. X-Git-Tag: REL9_1_ALPHA4~278 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=7212c77d0cabcc468fec0b9cd7f2413b64b77050;p=thirdparty%2Fpostgresql.git ALTER TABLE sometimes takes only ShareUpdateExclusiveLock. Along the way, be more consistent about the wording we use here. --- diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml index 152b7466b8b..579425dad64 100644 --- a/doc/src/sgml/mvcc.sgml +++ b/doc/src/sgml/mvcc.sgml @@ -656,7 +656,8 @@ SELECT SUM(value) FROM mytab WHERE class = 2; Acquired by VACUUM (without ), - ANALYZE, and CREATE INDEX CONCURRENTLY. + ANALYZE, CREATE INDEX CONCURRENTLY, and + some forms of ALTER TABLE. @@ -699,7 +700,7 @@ SELECT SUM(value) FROM mytab WHERE class = 2; Acquired by CREATE TRIGGER, CREATE RULE (except for ON SELECT - rules) and in some cases ALTER TABLE. + rules) and some forms of ALTER TABLE. @@ -747,7 +748,7 @@ SELECT SUM(value) FROM mytab WHERE class = 2; Acquired by the DROP TABLE, TRUNCATE, REINDEX, CLUSTER, and VACUUM FULL - commands, as well as most variants of ALTER TABLE. + commands, and some forms of ALTER TABLE. This is also the default lock mode for LOCK TABLE statements that do not specify a mode explicitly.