DOC: replaced productname instanced with project entity where applicable

Author: Liudmila Mantrova

doc/src/sgml/acronyms.sgml

@@ -4,8 +4,8 @@
  <title>Acronyms</title>
 
  <para>
-  This is a list of acronyms commonly used in the <productname>&productname;</>
-  documentation and in discussions about <productname>&productname;</>.
+  This is a list of acronyms commonly used in the <productname>&project;</>
+  documentation and in discussions about <productname>&project;</>.
 
   <variablelist>
 
@@ -185,7 +185,7 @@
     <term><acronym>ECPG</acronym></term>
     <listitem>
      <para>
-      <link linkend="ecpg">Embedded C for &productname;</link>
+      <link linkend="ecpg">Embedded C for &project;</link>
      </para>
     </listitem>
    </varlistentry>
@@ -281,7 +281,7 @@
     <listitem>
      <para>
       <link linkend="config-setting">Grand Unified Configuration</link>,
-      the <productname>&productname;</> subsystem that handles server configuration
+      the <productname>&project;</> subsystem that handles server configuration
      </para>
     </listitem>
    </varlistentry>
@@ -486,7 +486,7 @@
     <term><acronym>PGSQL</acronym></term>
     <listitem>
      <para>
-      <link linkend="postgres"><productname>&productname;</></link>
+      <link linkend="postgres"><productname>&project;</></link>
      </para>
     </listitem>
    </varlistentry>
@@ -495,7 +495,7 @@
     <term><acronym>PGXS</acronym></term>
     <listitem>
      <para>
-      <link linkend="extend-pgxs"><productname>&productname;</> Extension System</link>
+      <link linkend="extend-pgxs"><productname>&project;</> Extension System</link>
      </para>
     </listitem>
    </varlistentry>

doc/src/sgml/advanced.sgml

@@ -9,10 +9,10 @@
    <para>
     In the previous chapter we have covered the basics of using
     <acronym>SQL</acronym> to store and access your data in
-    <productname>&productname;</productname>.  We will now discuss some
+    <productname>&project;</productname>.  We will now discuss some
     more advanced features of <acronym>SQL</acronym> that simplify
     management and prevent loss or corruption of your data.  Finally,
-    we will look at some <productname>&productname;</productname>
+    we will look at some <productname>&project;</productname>
     extensions.
    </para>
 
@@ -93,7 +93,7 @@ SELECT * FROM myview;
     exists, and then inserting or rejecting the new
     <classname>weather</classname> records.  This approach has a
     number of problems and is very inconvenient, so
-    <productname>&productname;</productname> can do this for you.
+    <productname>&project;</productname> can do this for you.
    </para>
 
    <para>
@@ -216,7 +216,7 @@ UPDATE branches SET balance = balance + 100.00
    </para>
 
    <para>
-    In <productname>&productname;</>, a transaction is set up by surrounding
+    In <productname>&project;</>, a transaction is set up by surrounding
     the SQL commands of the transaction with
     <command>BEGIN</> and <command>COMMIT</> commands.  So our banking
     transaction would actually look like:
@@ -238,7 +238,7 @@ COMMIT;
    </para>
 
    <para>
-    <productname>&productname;</> actually treats every SQL statement as being
+    <productname>&project;</> actually treats every SQL statement as being
     executed within a transaction.  If you do not issue a <command>BEGIN</>
     command,
     then each individual statement has an implicit <command>BEGIN</> and
@@ -627,10 +627,10 @@ CREATE TABLE capitals (
     <structfield>population</>, and <structfield>altitude</>) from its
     <firstterm>parent</firstterm>, <classname>cities</classname>.  The
     type of the column <structfield>name</structfield> is
-    <type>text</type>, a native <productname>&productname;</productname>
+    <type>text</type>, a native <productname>&project;</productname>
     type for variable length character strings.  State capitals have
     an extra column, <structfield>state</>, that shows their state.  In
-    <productname>&productname;</productname>, a table can inherit from
+    <productname>&project;</productname>, a table can inherit from
     zero or more other tables.
    </para>
 
@@ -702,7 +702,7 @@ SELECT name, altitude
    <title>Conclusion</title>
 
    <para>
-    <productname>&productname;</productname> has many features not
+    <productname>&project;</productname> has many features not
     touched upon in this tutorial introduction, which has been
     oriented toward newer users of <acronym>SQL</acronym>.  These
     features are discussed in more detail in the remainder of this

doc/src/sgml/amcheck.sgml

@@ -193,20 +193,20 @@ ORDER BY c.relpages DESC LIMIT 10;
      <emphasis>indexed</> values might happen to have the same
      absolute ordering regardless of the behavioral inconsistency. See
      <xref linkend="locale"> and <xref linkend="collation"> for
-     further details about how <productname>&productname;</> uses
+     further details about how <productname>&project;</> uses
      operating system locales and collations.
     </para>
    </listitem>
    <listitem>
     <para>
      Corruption caused by hypothetical undiscovered bugs in the
-     underlying <productname>&productname;</> access method code or sort
+     underlying <productname>&project;</> access method code or sort
      code.
     </para>
     <para>
      Automatic verification of the structural integrity of indexes
      plays a role in the general testing of new or proposed
-     <productname>&productname;</> features that could plausibly allow a
+     <productname>&project;</> features that could plausibly allow a
      logical inconsistency to be introduced.  One obvious testing
      strategy is to call <filename>amcheck</> functions continuously
      when running the standard regression tests.  See <xref
@@ -234,7 +234,7 @@ ORDER BY c.relpages DESC LIMIT 10;
      and operating system.
     </para>
     <para>
-     <productname>&productname;</> does not protect against correctable
+     <productname>&project;</> does not protect against correctable
      memory errors and it is assumed you will operate using RAM that
      uses industry standard Error Correcting Codes (ECC) or better
      protection.  However, ECC memory is typically only immune to

doc/src/sgml/arch-dev.sgml

@@ -1,7 +1,7 @@
 <!-- doc/src/sgml/arch-dev.sgml -->
 
  <chapter id="overview">
-  <title>Overview of &productname; Internals</title>
+  <title>Overview of &project; Internals</title>
 
   <note>
    <title>Author</title>
@@ -15,11 +15,11 @@
 
   <para>
    This chapter gives an overview of the internal structure of the
-   backend of <productname>&productname;</productname>.  After having
+   backend of <productname>&project;</productname>.  After having
    read the following sections you should have an idea of how a query
    is processed. This chapter does not aim to provide a detailed
    description of the internal operation of
-   <productname>&productname;</productname>, as such a document would be
+   <productname>&project;</productname>, as such a document would be
    very extensive. Rather, this chapter is intended to help the reader
    understand the general sequence of operations that occur within the
    backend from the point at which a query is received, to the point
@@ -37,7 +37,7 @@
    <procedure>
     <step>
      <para>
-      A connection from an application program to the <productname>&productname;</productname>
+      A connection from an application program to the <productname>&project;</productname>
       server has to be established. The application program transmits a
       query to the server and waits to receive the results sent back by the
       server.
@@ -108,7 +108,7 @@
 
    <para>
     In the following sections we will cover each of the above listed items
-    in more detail to give a better understanding of <productname>&productname;</productname>'s internal
+    in more detail to give a better understanding of <productname>&project;</productname>'s internal
     control and data structures.
    </para>
   </sect1>
@@ -117,7 +117,7 @@
    <title>How Connections are Established</title>
 
    <para>
-    <productname>&productname;</productname> is implemented using a
+    <productname>&project;</productname> is implemented using a
     simple <quote>process per user</> client/server model.  In this model
     there is one <firstterm>client process</firstterm> connected to
     exactly one <firstterm>server process</firstterm>.  As we do not
@@ -135,7 +135,7 @@
 
    <para>
     The client process can be any program that understands the
-    <productname>&productname;</productname> protocol described in
+    <productname>&project;</productname> protocol described in
     <xref linkend="protocol">.  Many clients are based on the
     C-language library <application>libpq</>, but several independent
     implementations of the protocol exist, such as the Java
@@ -220,7 +220,7 @@
       <para>
        The mentioned transformations and compilations are normally done
        automatically using the <firstterm>makefiles</firstterm>
-       shipped with the <productname>&productname;</productname>
+       shipped with the <productname>&project;</productname>
        source distribution.
       </para>
      </note>
@@ -282,13 +282,13 @@
   </sect1>
 
   <sect1 id="rule-system">
-   <title>The <productname>&productname;</productname> Rule System</title>
+   <title>The <productname>&project;</productname> Rule System</title>
 
    <para>
-    <productname>&productname;</productname> supports a powerful
+    <productname>&project;</productname> supports a powerful
     <firstterm>rule system</firstterm> for the specification
     of <firstterm>views</firstterm> and ambiguous <firstterm>view updates</firstterm>.
-    Originally the <productname>&productname;</productname>
+    Originally the <productname>&project;</productname>
     rule system consisted of two implementations:
 
     <itemizedlist>
@@ -346,7 +346,7 @@
      space. In particular, this occurs when executing queries
      involving large numbers of join operations. In order to determine
      a reasonable (not necessarily optimal) query plan in a reasonable amount
-     of time, <productname>&productname;</productname> uses a <firstterm>Genetic
+     of time, <productname>&project;</productname> uses a <firstterm>Genetic
      Query Optimizer</firstterm> (see <xref linkend="geqo">) when the number of joins
      exceeds a threshold (see <xref linkend="guc-geqo-threshold">).
     </para>

doc/src/sgml/array.sgml

@@ -8,7 +8,7 @@
  </indexterm>
 
  <para>
-  <productname>&productname;</productname> allows columns of a table to be
+  <productname>&project;</productname> allows columns of a table to be
   defined as variable-length multidimensional arrays. Arrays of any
   built-in or user-defined base type, enum type, or composite type
   can be created.
@@ -80,7 +80,7 @@ CREATE TABLE tictactoe (
 <programlisting>
     pay_by_quarter  integer ARRAY,
 </programlisting>
-  As before, however, <productname>&productname;</> does not enforce the
+  As before, however, <productname>&project;</> does not enforce the
   size restriction in any case.
  </para>
  </sect2>
@@ -107,7 +107,7 @@ CREATE TABLE tictactoe (
    where <replaceable>delim</replaceable> is the delimiter character
    for the type, as recorded in its <literal>pg_type</literal> entry.
    Among the standard data types provided in the
-   <productname>&productname;</productname> distribution, all use a comma
+   <productname>&project;</productname> distribution, all use a comma
    (<literal>,</>), except for type <type>box</> which uses a semicolon
    (<literal>;</>). Each <replaceable>val</replaceable> is
    either a constant of the array element type, or a subarray. An example
@@ -221,7 +221,7 @@ SELECT name FROM sal_emp WHERE pay_by_quarter[1] &lt;&gt; pay_by_quarter[2];
 </programlisting>
 
   The array subscript numbers are written within square brackets.
-  By default <productname>&productname;</productname> uses a
+  By default <productname>&project;</productname> uses a
   one-based numbering convention for arrays, that is,
   an array of <replaceable>n</> elements starts with <literal>array[1]</literal> and
   ends with <literal>array[<replaceable>n</>]</literal>.
@@ -709,7 +709,7 @@ SELECT array_positions(ARRAY[1, 4, 3, 1, 3, 4, 2, 1], 1);
    The delimiter character is usually a comma (<literal>,</>) but can be
    something else: it is determined by the <literal>typdelim</> setting
    for the array's element type.  Among the standard data types provided
-   in the <productname>&productname;</productname> distribution, all use a comma,
+   in the <productname>&project;</productname> distribution, all use a comma,
    except for type <type>box</>, which uses a semicolon (<literal>;</>).
    In a multidimensional array, each dimension (row, plane,
    cube, etc.) gets its own level of curly braces, and delimiters