11<!--
2- $Header: /cvsroot/pgsql/doc/src/sgml/ref/lock.sgml,v 1.15 2000/03/2321:38:57 momjian Exp $
2+ $Header: /cvsroot/pgsql/doc/src/sgml/ref/lock.sgml,v 1.16 2000/03/2322:25:35 momjian Exp $
33Postgres documentation
44-->
55
@@ -123,7 +123,7 @@ LOCK [ TABLE ] <replaceable class="PARAMETER">name</replaceable> IN SHARE ROW EX
123123 </note>
124124
125125 <para>
126- This is the least restrictive lock mode which conflicts only with
126+ This is the least restrictive lock mode. It conflicts only with
127127ACCESS EXCLUSIVE mode. It is intended to protect a table being
128128modified by concurrent <command>ALTER TABLE</command>,
129129<command>DROP TABLE</command> and <command>VACUUM</command>
@@ -137,8 +137,8 @@ LOCK [ TABLE ] <replaceable class="PARAMETER">name</replaceable> IN SHARE ROW EX
137137 <listitem>
138138 <note>
139139 <para>
140- Automatically acquired byany <command>SELECT FOR UPDATE</command> statement .
141- While it is aSHARE lock, there is the intention to later upgrade
140+ Automatically acquired by <command>SELECT... FOR UPDATE</command>.
141+ While it is ashared lock, there is the intention to later upgrade
142142 this to an EXCLUSIVE lock.
143143</para>
144144 </note>
@@ -154,15 +154,15 @@ LOCK [ TABLE ] <replaceable class="PARAMETER">name</replaceable> IN SHARE ROW EX
154154 <listitem>
155155 <note>
156156<para>
157- Automatically acquired by any <command>UPDATE</command>,
158- <command>DELETE</command>, <command>INSERT</command> statement.
157+ Automatically acquired by <command>UPDATE</command>,
158+ <command>DELETE</command>, and <command>INSERT</command>
159+ statements.
159160 </para>
160161 </note>
161162
162163 <para>
163164 Conflicts with SHARE, SHARE ROW EXCLUSIVE, EXCLUSIVE and
164- ACCESS EXCLUSIVE modes. Generally means that a transaction
165- updated or inserted some tuples in a table.
165+ ACCESS EXCLUSIVE modes.
166166 </para>
167167 </listitem>
168168 </varlistentry>
@@ -172,8 +172,8 @@ LOCK [ TABLE ] <replaceable class="PARAMETER">name</replaceable> IN SHARE ROW EX
172172 <listitem>
173173 <note>
174174 <para>
175- Automatically acquired byany <command>CREATE INDEX</command> statement .
176- Share-locks entire table.
175+ Automatically acquired by <command>CREATE INDEX</command>.
176+ Share-locksthe entire table.
177177 </para>
178178 </note>
179179
@@ -188,10 +188,14 @@ LOCK [ TABLE ] <replaceable class="PARAMETER">name</replaceable> IN SHARE ROW EX
188188 <varlistentry>
189189 <term>SHARE ROW EXCLUSIVE MODE</term>
190190 <listitem>
191-
191+ <note>
192192 <para>
193- This is likean EXCLUSIVElock , but allows SHARE ROW locks
193+ This is like EXCLUSIVEMODE , but allows SHARE ROW locks
194194 by others.
195+ </para>
196+ </note>
197+
198+ <para>
195199 Conflicts with ROW EXCLUSIVE, SHARE, SHARE ROW EXCLUSIVE,
196200EXCLUSIVE and ACCESS EXCLUSIVE modes.
197201 </para>
@@ -202,11 +206,16 @@ LOCK [ TABLE ] <replaceable class="PARAMETER">name</replaceable> IN SHARE ROW EX
202206 <term>EXCLUSIVE MODE</term>
203207 <listitem>
204208
209+ <note>
210+ <para>
211+ This mode is yet more restrictive than SHARE ROW EXCLUSIVE.
212+ It blocks all concurrent ROW SHARE/SELECT...FOR UPDATE queries.
213+ </para>
214+ </note>
215+
205216 <para>
206217Conflicts with ROW SHARE, ROW EXCLUSIVE, SHARE, SHARE ROW EXCLUSIVE,
207- EXCLUSIVE and ACCESS EXCLUSIVE modes. This mode is yet more
208- restrictive than that of SHARE ROW EXCLUSIVE; it blocks all concurrent
209- SHARE ROW/SELECT FOR UPDATE queries.
218+ EXCLUSIVE and ACCESS EXCLUSIVE modes.
210219 </para>
211220 </listitem>
212221 </varlistentry>
@@ -218,14 +227,11 @@ LOCK [ TABLE ] <replaceable class="PARAMETER">name</replaceable> IN SHARE ROW EX
218227<para>
219228 Automatically acquired by <command>ALTER TABLE</command>,
220229 <command>DROP TABLE</command>, <command>VACUUM</command> statements.
230+ This is the most restrictive lock mode which conflicts with all other
231+ lock modes and protects a locked table from any concurrent operations.
221232</para>
222233 </note>
223234
224- <para>
225- This is the most restrictive lock mode which conflicts with all other
226- lock modes and protects a locked table from any concurrent operations.
227- </para>
228-
229235 <note>
230236<para>
231237 This lock mode is also acquired by an unqualified