[Doc]: fix productname in pgpathman.sgml

dmpgpro · dmpgpro · commit 5a9a62c48e5b · 2016-10-07T20:40:45.000+03:00
diff --git a/doc/src/sgml/pgpathman.sgml b/doc/src/sgml/pgpathman.sgml
@@ -5,16 +5,15 @@
     partitioning mechanism and functions to manage partitions.
   </para>
   <para>
-    The extension is compatible with &productname; 9.5 (9.6 support is
-    coming soon).
+    The extension is compatible with &productname; 9.5, 9.6.
   </para>
   <sect2 id="pg-pathman-overview">
     <title>Overview</title>
     <para>
       <emphasis role="strong">Partitioning</emphasis> means splitting
       one large table into smaller pieces. Each row in such table is
       moved to a single partition according to the partitioning key.
-      &productname; supports partitioning via table inheritance: each
+      PostgreSQL supports partitioning via table inheritance: each
       partition must be created as a child table with CHECK CONSTRAINT.
       For example:
     </para>
@@ -128,7 +127,7 @@ CREATE EXTENSION pg_pathman;
         <emphasis role="strong">Important:</emphasis> Don't forget to
         set the <literal>PG_CONFIG</literal> variable in case you want
         to test <literal>pg_pathman</literal> on a custom build of
-        &productname;. Read more
+        PostgreSQL. Read more
         <ulink url="https://wiki.postgresql.org/wiki/Building_and_Installing_PostgreSQL_Extension_Modules">here</ulink>.
       </para>
     </blockquote>
@@ -344,7 +343,7 @@ set_enable_parent(relation REGCLASS, value BOOLEAN)
 </programlisting>
       <para>
         Include/exclude parent table into/from query plan. In original
-        &productname; planner parent table is always included into query
+        PostgreSQL planner parent table is always included into query
         plan even if it's empty which can lead to additional overhead.
         You can use <literal>disable_parent()</literal> if you are never
         going to use parent table as a storage. Default value depends on
@@ -968,7 +967,7 @@ WHERE id = any (SELECT * FROM some_table limit 4);
       </programlisting>
       <para>
         All sections and data will remain unchanged and will be handled
-        by the standard &productname; inheritance mechanism.
+        by the standard PostgreSQL inheritance mechanism.
       </para>
     </sect3>
   </sect2>
