Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit 33862cb

Browse filesBrowse files
tglsfdctglsfdc
committed
Doc: undo mistaken adjustment to LOCK TABLE docs in back branches.
Commits 59ab4ac 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
1 parent 9d878d7 commit 33862cb
Copy full SHA for 33862cb

File tree

Expand file treeCollapse file tree

1 file changed

+7
-2
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+7
-2
lines changed

‎doc/src/sgml/ref/lock.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/ref/lock.sgml
+7-2Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -117,8 +117,13 @@ LOCK [ TABLE ] [ ONLY ] <replaceable class="PARAMETER">name</replaceable> [ * ]
117117
table is locked. If <literal>ONLY</literal> is not specified, the table and all
118118
its descendant tables (if any) are locked. Optionally, <literal>*</literal>
119119
can be specified after the table name to explicitly indicate that
120-
descendant tables are included. When locking a view, all relations appearing
121-
in the view definition are locked, regardless of <literal>ONLY</literal>.
120+
descendant tables are included.
121+
</para>
122+
123+
<para>
124+
Locking a view locks only the view object itself, not any referenced
125+
relations. (Note that this behavior is different
126+
in <productname>PostgreSQL</productname> v11 and later.)
122127
</para>
123128

124129
<para>

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.