postgres.git / summary / log / commit / refs

commit    583fcf2f57594cc73fe537b2bf18cfbc6b13336f
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Fri Nov 06 17:14:46 2020 +0000
First released in: 9.5.24, 9.6.20, 10.15

    Doc: undo mistaken adjustment to LOCK TABLE docs in back branches.
    
    Commits 59ab4ac32 et al mistakenly copied-and-pasted some text about
    how LOCK on a view recurses to referenced tables into pre-v11 branches,
    which in fact don't do that.  Undo that, and instead state clearly
    that they don't.  (I also chose to add a note that this behavior
    changed in v11.  We usually don't back-patch such statements, but
    since it's easy to add the warning now, might as well.)
    
    Noted while considering followup fixes for bug #16703.
    
    Discussion: https://postgr.es/m/16703-e348f58aab3cf6cc@postgresql.org


 doc/src/sgml/ref/lock.sgml | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml
index 7f40177129c..9b33ddc637c 100644
--- a/doc/src/sgml/ref/lock.sgml
+++ b/doc/src/sgml/ref/lock.sgml
@@ -117,8 +117,13 @@ LOCK [ TABLE ] [ ONLY ] <replaceable class="PARAMETER">name</replaceable> [ * ]
       table is locked. If <literal>ONLY</literal> is not specified, the table and all
       its descendant tables (if any) are locked.  Optionally, <literal>*</literal>
       can be specified after the table name to explicitly indicate that
-      descendant tables are included.  When locking a view, all relations appearing
-      in the view definition are locked, regardless of <literal>ONLY</literal>.
+      descendant tables are included.
+     </para>
+
+     <para>
+      Locking a view locks only the view object itself, not any referenced
+      relations.  (Note that this behavior is different
+      in <productname>PostgreSQL</productname> v11 and later.)
      </para>
 
      <para>


[parent: 04c4b495b1c9]