Adjust documentation wording of window function ORDER BY to not mention

avg() because it was inaccurate.

diff --git a/doc/src/sgml/advanced.sgml b/doc/src/sgml/advanced.sgml
index 11859b4e30fa50301c859003af602e3d2c3a90d6..218988e0afc1173f8dba69f4e8f5ba7fdbcaaf31 100644 (file)
--- a/doc/src/sgml/advanced.sgml
+++ b/doc/src/sgml/advanced.sgml
@@ -383,10 +383,10 @@ SELECT depname, empno, salary, avg(salary) OVER (PARTITION BY depname) FROM emps
    
 
    
-    Although avg will produce the same result no matter
-    what order it processes the partition's rows in, this is not true of all
-    window functions.  When needed, you can control that order using
-    ORDER BY within OVER.  Here is an example:
+    You can also control the order in which rows are processed by
+    window functions using ORDER BY within OVER.
+    (The window ORDER BY does not even have to match the
+    order in which the rows are output.)  Here is an example:
 
 
 SELECT depname, empno, salary, rank() OVER (PARTITION BY depname ORDER BY salary DESC) FROM empsalary;