docs: specify FOR UPDATE/SHARE incompatibilities

Document that FOR UPDATE/SHARE are incompatible with GROUP BY, DISTINCT,
HAVING and window functions.

Michael Paquier

diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml
index f9f83f34f70d90f503c16f7d2256a9ceabd8d6f1..9a468b98c0a750cf6c2f7c75ad2add3640c59841 100644 (file)
--- a/doc/src/sgml/ref/select.sgml
+++ b/doc/src/sgml/ref/select.sgml
@@ -654,6 +654,12 @@ GROUP BY expression [, ...]
     the grouped columns (or a subset thereof) are the primary key of
     the table containing the ungrouped column.
    
+
+   
+    Currently, FOR NO KEY UPDATE, FOR UPDATE,
+    FOR SHARE and FOR KEY SHARE cannot be
+    specified with GROUP BY.
+   
   
 
   
@@ -690,6 +696,12 @@ HAVING condition
     within aggregate functions.  Such a query will emit a single row if the
     HAVING condition is true, zero rows if it is not true.
    
+
+   
+    Currently, FOR NO KEY UPDATE, FOR UPDATE,
+    FOR SHARE and FOR KEY SHARE cannot be
+    specified with HAVING.
+   
   
 
   
@@ -824,6 +836,12 @@ UNBOUNDED FOLLOWING
     than one window function.
    
 
+   
+    Currently, FOR NO KEY UPDATE, FOR UPDATE,
+    FOR SHARE and FOR KEY SHARE cannot be
+    specified with WINDOW.
+   
+
    
     Window functions are described in detail in
     ,
@@ -920,6 +938,12 @@ SELECT DISTINCT ON (location) location, time, report
     will normally contain additional expression(s) that determine the
     desired precedence of rows within each DISTINCT ON group.
    
+
+   
+    Currently, FOR NO KEY UPDATE, FOR UPDATE,
+    FOR SHARE and FOR KEY SHARE cannot be
+    specified with DISTINCT.
+