diff options
author | Peter Eisentraut | 2017-10-15 13:14:08 +0000 |
---|---|---|
committer | Peter Eisentraut | 2017-10-15 13:14:08 +0000 |
commit | d8794fd7c337a2285f46b23d348c9826afff69eb (patch) | |
tree | a812763078fe4b93535accad8db5ab8a3f5e32a8 | |
parent | 82aff8d3369754282114cb0fff92a342b2864e75 (diff) |
doc: Postgres -> PostgreSQL
-rw-r--r-- | doc/src/sgml/ref/create_aggregate.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/ref/create_aggregate.sgml b/doc/src/sgml/ref/create_aggregate.sgml index 4d9c8b0b70..ee79c90df2 100644 --- a/doc/src/sgml/ref/create_aggregate.sgml +++ b/doc/src/sgml/ref/create_aggregate.sgml @@ -666,7 +666,7 @@ SELECT col FROM tab ORDER BY col USING sortop LIMIT 1; </para> <para> - Ordinarily, Postgres functions are expected to be true functions that + Ordinarily, PostgreSQL functions are expected to be true functions that do not modify their input values. However, an aggregate transition function, <emphasis>when used in the context of an aggregate</>, is allowed to cheat and modify its transition-state argument in place. |