Apply productname extension path

dmpgpro · dmpgpro · commit 6395876f8b1b · 2016-10-07T12:22:50.000+03:00
diff --git a/doc/src/sgml/dump-stat.sgml b/doc/src/sgml/dump-stat.sgml
@@ -21,7 +21,7 @@
         Note that the definition of the
         <link linkend="catalog-pg-statistic"><structname>pg_statistic</structname></link>
         table might change occasionally, which means that generated dump might be incompatible
-        with future releases of <productname>PostgreSQL</productname>.
+        with future releases of <productname>&productname;</productname>.
     </para>
 
     <sect2>
diff --git a/doc/src/sgml/pg_variables.sgml b/doc/src/sgml/pg_variables.sgml
@@ -527,7 +527,7 @@ ERROR:  variable "int1" requires "integer" value
       </informaltable>
       <para>
         Note that <literal>pgv_stats()</literal> works only with the
-        PostgreSQL 9.6 and newer.
+        &productname; 9.6 and newer.
       </para>
     </sect3>
   </sect2>
diff --git a/doc/src/sgml/pgpathman.sgml b/doc/src/sgml/pgpathman.sgml
@@ -5,7 +5,7 @@
     partitioning mechanism and functions to manage partitions.
   </para>
   <para>
-    The extension is compatible with PostgreSQL 9.5 (9.6 support is
+    The extension is compatible with &productname; 9.5 (9.6 support is
     coming soon).
   </para>
   <sect2 id="pg-pathman-overview">
@@ -14,7 +14,7 @@
       <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.
-      PostgreSQL supports partitioning via table inheritance: each
+      &productname; supports partitioning via table inheritance: each
       partition must be created as a child table with CHECK CONSTRAINT.
       For example:
     </para>
@@ -114,7 +114,7 @@ make install USE_PGXS=1
 shared_preload_libraries = 'pg_pathman'
 </programlisting>
     <para>
-      It is essential to restart the PostgreSQL instance. After that,
+      It is essential to restart the &productname; instance. After that,
       execute the following query in psql:
     </para>
     <programlisting>
@@ -128,7 +128,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
-        PostgreSQL. Read more
+        &productname;. Read more
         <ulink url="https://wiki.postgresql.org/wiki/Building_and_Installing_PostgreSQL_Extension_Modules">here</ulink>.
       </para>
     </blockquote>
@@ -344,7 +344,7 @@ set_enable_parent(relation REGCLASS, value BOOLEAN)
 </programlisting>
       <para>
         Include/exclude parent table into/from query plan. In original
-        PostgreSQL planner parent table is always included into query
+        &productname; 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
@@ -961,7 +961,7 @@ SELECT disable_pathman_for('range_rel');
 </programlisting>
       <para>
         All sections and data will remain unchanged and will be handled
-        by the standard PostgreSQL inheritance mechanism.
+        by the standard &productname; inheritance mechanism.
       </para>
     </sect3>
   </sect2>
