Doc: sync with EE - productname fixes from A.Lakhin

Liudmila Mantrova · Liudmila Mantrova · commit 0f83eeed91ab · 2017-05-03T15:36:48.000+03:00
diff --git a/doc/src/sgml/mchar.sgml b/doc/src/sgml/mchar.sgml
@@ -23,7 +23,7 @@
     MS-SQL behavoir concerning end-of-value whitespace.
     </para>
     <para>
-    Differences from PostgreSQL standard CHAR and VARCHAR are:
+    Differences from &productname; standard CHAR and VARCHAR are:
     </para>
     <itemizedlist>
     <listitem>
diff --git a/doc/src/sgml/plantuner.sgml b/doc/src/sgml/plantuner.sgml
@@ -11,20 +11,21 @@
       Whether somebody think it's bad or not, but sometime it's very
       interesting to be able to control planner (provide hints, which tell
       optimizer to ignore its algorithm in part), which is currently
-      impossible in PostgreSQL. Oracle, for example, has over 120 hints,
+      impossible in &productname; (and PostgreSQL).
+      Oracle, for example, has over 120 hints,
       and Microsoft SQL Server also supports hints.
     </para>
     <para>
       This first version of plantuner provides a possibility to hide
-      specified indexes from PostgreSQL planner, so it will not use them.
+      specified indexes from &productname; planner, so it will not use them.
     </para>
     <para>
       There are many situations when developer want to temporarily disable
       specific index(es), without dropping them, or to instruct planner to
       use specific index.
     </para>
     <para>
-      Next, for some workload PostgreSQL could be too pessimistic for
+      Next, for some workload &productname; could be too pessimistic for
       newly created tables and assumes much more rows in table than
       it actually has. If plantuner.fix_empty_table GUC variable is set
       to true then module will set to zero the number of pages/tuples of
diff --git a/doc/src/sgml/ref/waitlsn.sgml b/doc/src/sgml/ref/waitlsn.sgml
@@ -1,6 +1,6 @@
 <!--
 doc/src/sgml/ref/waitlsn.sgml
-PostgreSQL documentation
+&productname; documentation
 -->
 
 <refentry id="SQL-WAITLSN">
@@ -37,7 +37,7 @@ WAITLSN <replaceable class="PARAMETER">'LSN'</replaceable> [ , <replaceable clas
   <para>
    <command>WAITLSN</command> provides a simple
    interprocess <acronym>LSN</> wait mechanism for a backends on slave
-   in master-slave replication scheme on <productname>PostgreSQL</productname> database.
+   in master-slave replication scheme on <productname>&productname;</productname> database.
   </para>
  </refsect1>
 
diff --git a/doc/src/sgml/rowtypes.sgml b/doc/src/sgml/rowtypes.sgml
@@ -260,7 +260,7 @@ INSERT INTO mytab (complex_col.r, complex_col.i) VALUES(1.1, 2.2);
   </para>
 
   <para>
-   In <productname>PostgreSQL</>, a reference to a table name (or alias)
+   In <productname>&productname;</>, a reference to a table name (or alias)
    in a query is effectively a reference to the composite value of the
    table's current row.  For example, if we had a table
    <structname>inventory_item</> as shown
@@ -306,7 +306,7 @@ SELECT c.* FROM inventory_item c;
 <programlisting>
 SELECT c.name, c.supplier_id, c.price FROM inventory_item c;
 </programlisting>
-   <productname>PostgreSQL</> will apply this expansion behavior to
+   <productname>&productname;</> will apply this expansion behavior to
    any composite-valued expression, although as shown <link
    linkend="rowtypes-accessing">above</link>, you need to write parentheses
    around the value that <literal>.*</> is applied to whenever it's not a
@@ -322,7 +322,7 @@ SELECT (myfunc(x)).a, (myfunc(x)).b, (myfunc(x)).c FROM some_table;
 
   <tip>
    <para>
-    <productname>PostgreSQL</> handles column expansion by
+    <productname>&productname;</> handles column expansion by
     actually transforming the first form into the second.  So, in this
     example, <function>myfunc()</> would get invoked three times per row
     with either syntax.  If it's an expensive function you may wish to
