From d8794fd7c337a2285f46b23d348c9826afff69eb Mon Sep 17 00:00:00 2001
From: Peter Eisentraut <peter_e@gmx.net>
Date: Sun, 15 Oct 2017 09:14:08 -0400
Subject: [PATCH] doc: Postgres -> PostgreSQL

---
 doc/src/sgml/ref/create_aggregate.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/create_aggregate.sgml b/doc/src/sgml/ref/create_aggregate.sgml
index 4d9c8b0b707..ee79c90df2b 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.