doc: use simpler language for NULL return from ANY/ALL

Previously the combination of "does not return" and "any row" caused
ambiguity.

Reported-by: KES 
Discussion: https://postgr.es/m/153701242703.22334.1476830122267077397@wrigleys.postgresql.org

Reviewed-by: David G. Johnston
Backpatch-through: 9.3

diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 92eb084d3c23a13eddec8eb7ba5490e05a9fb87d..87e12439827a4e5b3a2b7e8fc6bdd372e019c690 100644 (file)
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -14620,7 +14620,7 @@ WHERE EXISTS (SELECT 1 FROM tab2 WHERE col2 = tab1.col2);
    The result is false if the comparison returns false for every
    subquery row (including the case where the subquery returns no
    rows).
-   The result is NULL if the comparison does not return true for any row,
+   The result is NULL if no comparison with a subquery row returns true,
    and it returns NULL for at least one row.
   
 
@@ -14646,7 +14646,7 @@ WHERE EXISTS (SELECT 1 FROM tab2 WHERE col2 = tab1.col2);
    The result of ALL is true if all rows yield true
    (including the case where the subquery returns no rows).
    The result is false if any false result is found.
-   The result is NULL if the comparison does not return false for any row,
+   The result is NULL if no comparison with a subquery row returns false,
    and it returns NULL for at least one row.
   
 
@@ -14676,8 +14676,8 @@ WHERE EXISTS (SELECT 1 FROM tab2 WHERE col2 = tab1.col2);
    case where the subquery returns no rows).
    The result is false if the comparison returns false for any
    subquery row.
-   The result is NULL if the comparison does not return false for any
-   subquery row, and it returns NULL for at least one row.
+   The result is NULL if no comparison with a subquery row returns false,
+   and it returns NULL for at least one row.