aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2011-01-21 12:57:49 -0500
committerRobert Haas <rhaas@postgresql.org>2011-01-21 12:59:15 -0500
commitd3b372e92d4efdd6f63da35996f04ff009c932b5 (patch)
treed93ff2d5b42a3d334d62a171ce724450b42e4d71
parent5925aa09a9110fe0d12393c758812e7149546443 (diff)
downloadpostgresql-d3b372e92d4efdd6f63da35996f04ff009c932b5.tar.gz
postgresql-d3b372e92d4efdd6f63da35996f04ff009c932b5.zip
Emphasize where OVER needs to be when using a window function.
Jeff Turner
-rw-r--r--doc/src/sgml/advanced.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/advanced.sgml b/doc/src/sgml/advanced.sgml
index 784b40a3621..9cb717313a8 100644
--- a/doc/src/sgml/advanced.sgml
+++ b/doc/src/sgml/advanced.sgml
@@ -371,7 +371,7 @@ SELECT depname, empno, salary, avg(salary) OVER (PARTITION BY depname) FROM emps
<para>
A window function call always contains an <literal>OVER</> clause
- following the window function's name and argument(s). This is what
+ directly following the window function's name and argument(s). This is what
syntactically distinguishes it from a regular function or aggregate
function. The <literal>OVER</> clause determines exactly how the
rows of the query are split up for processing by the window function.