Replaced &productname; with explicit PostgreSQL where it refers to prior releases

vbwagner · vbwagner · commit 185ed03318a2 · 2016-05-04T12:43:56.000+03:00
diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
@@ -4108,7 +4108,7 @@
   </para>
 
   <para>
-   Prior to <productname>&productname;</> 9.0, there was no permission structure
+   Prior to <productname>PostgreSQL</> 9.0, there was no permission structure
    associated with large objects.  As a result,
    <structname>pg_largeobject</structname> was publicly readable and could be
    used to obtain the OIDs (and contents) of all large objects in the system.
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
@@ -14446,7 +14446,7 @@ AND
 
   <note>
    <para>
-    Prior to <productname>&productname;</productname> 8.2, the
+    Prior to <productname>PosgreSQL</productname> 8.2, the
     <literal>&lt;</>, <literal>&lt;=</>, <literal>&gt;</> and <literal>&gt;=</>
     cases were not handled per SQL specification.  A comparison like
     <literal>ROW(a,b) &lt; ROW(c,d)</>
diff --git a/doc/src/sgml/hstore.sgml b/doc/src/sgml/hstore.sgml
@@ -209,7 +209,7 @@ key =&gt; NULL
 
   <note>
   <para>
-   Prior to &productname; 8.2, the containment operators <literal>@&gt;</>
+   Prior to PostgreSQL 8.2, the containment operators <literal>@&gt;</>
    and <literal>&lt;@</> were called <literal>@</> and <literal>~</>,
    respectively. These names are still available, but are deprecated and will
    eventually be removed. Notice that the old names are reversed from the
diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml
@@ -5855,7 +5855,7 @@ ORDER BY c.ordinal_position;
 
   <note>
    <para>
-    Prior to <productname>&productname;</> 9.1, this view's columns
+    Prior to <productname>PostgreSQL</> 9.1, this view's columns
     <structfield>action_timing</structfield>,
     <structfield>action_reference_old_table</structfield>,
     <structfield>action_reference_new_table</structfield>,
diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml
@@ -1579,7 +1579,7 @@ All of &productname; is successfully made. Ready to install.
     The standard installation provides all the header files needed for client
     application development as well as for server-side program
     development, such as custom functions or data types written in C.
-    (Prior to <productname>&productname;</> 8.0, a separate <literal>make
+    (Prior to <productname>PostgreSQL</> 8.0, a separate <literal>make
     install-all-headers</> command was needed for the latter, but this
     step has been folded into the standard install.)
    </para>
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
@@ -536,7 +536,7 @@ ERROR:  could not serialize access due to concurrent update
 
    <note>
     <para>
-     Prior to <productname>&productname;</productname> version 9.1, a request
+     Prior to <productname>PostgreSQL</productname> version 9.1, a request
      for the Serializable transaction isolation level provided exactly the
      same behavior described here.  To retain the legacy Serializable
      behavior, Repeatable Read should now be requested.
diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
@@ -616,7 +616,7 @@ Indexes:
   </para>
 
   <para>
-   Prior releases of <productname>&productname;</productname> also had an
+   Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
    it had no significant advantages over the GiST method.
    If <literal>USING rtree</> is specified, <command>CREATE INDEX</>
diff --git a/doc/src/sgml/ref/explain.sgml b/doc/src/sgml/ref/explain.sgml
@@ -105,7 +105,7 @@ ROLLBACK;
   <para>
    Only the <literal>ANALYZE</literal> and <literal>VERBOSE</literal> options
    can be specified, and only in that order, without surrounding the option
-   list in parentheses.  Prior to <productname>&productname;</productname> 9.0,
+   list in parentheses.  Prior to <productname>PostgreSQL</productname> 9.0,
    the unparenthesized syntax was the only one supported.  It is expected that
    all new options will be supported only in the parenthesized syntax.
   </para>
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
@@ -592,7 +592,7 @@ psql: could not connect to server: No such file or directory
 
    <note>
      <para>
-       Prior to <productname>&productname;</> 9.3, the amount of System V shared
+       Prior to <productname>PostgreSQL</> 9.3, the amount of System V shared
        memory required to start the server was much larger.  If you are running
        an older version of the server, please consult the documentation for
        your server version.
diff --git a/doc/src/sgml/xindex.sgml b/doc/src/sgml/xindex.sgml
@@ -1094,7 +1094,7 @@ ALTER OPERATOR FAMILY integer_ops USING btree ADD
 
   <note>
    <para>
-    Prior to <productname>&productname;</productname> 8.3, there was no concept
+    Prior to <productname>PostgreSQL</productname> 8.3, there was no concept
     of operator families, and so any cross-data-type operators intended to be
     used with an index had to be bound directly into the index's operator
     class.  While this approach still works, it is deprecated because it
