From 891497d3a9708eb773cd3bd9ff09de1beb9453fa Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sat, 26 Feb 2005 18:37:17 +0000
Subject: [PATCH] Correct overstatement in locking docs: we said ExclusiveLock
is never taken automatically, but this is only true with respect to user
tables.
---
doc/src/sgml/mvcc.sgml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index 01f697d426a..1aeec22b66c 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.46 2004/12/23 23:07:38 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.47 2005/02/26 18:37:17 tgl Exp $
-->
<chapter id="mvcc">
@@ -677,8 +677,9 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
</para>
<para>
- This lock mode is not automatically acquired by any
- <productname>PostgreSQL</productname> command.
+ This lock mode is not automatically acquired on user tables by any
+ <productname>PostgreSQL</productname> command. However it is
+ acquired on certain system catalogs in some operations.
</para>
</listitem>
</varlistentry>
--
GitLab