Merge branch 'PGPRO9_6' into PGPROEE9_6

Merge documentation fixes from PGPRO Standard 9.6.3.1

Author: vbwagner

contrib/fasttrun/fasttrun.control

@@ -2,4 +2,4 @@
 comment = 'Functions to truncates the temporary table and does not grow pg_class size'
 default_version = '1.0'
 module_pathname = '$libdir/fasttrun'
-relocatable = true
+relocatable = true

contrib/fulleq/fulleq.control

@@ -2,4 +2,4 @@
 comment = 'Introduce operator == which returns true when operands are equal or both are nulls.'
 default_version = '1.0'
 module_pathname = '$libdir/fulleq'
-relocatable = true
+relocatable = true

doc/src/sgml/config-one-c.sgml

@@ -30,7 +30,7 @@ temp_buffers = 32MB
         <programlisting>
 max_locks_per_transaction = 256
 </programlisting>
-        <para>Typically, <productname>1C</productname> solutions use a lot of temporary tables. Every backend process usually contains multiple temporary tables. When closing a connection, <productname>&productname;</productname> tries to drop all temporary tables in a single transactio, so this transaction may use a lot of locks. If the number of locks exceeds the <varname>max_locks_per_transaction</varname> value, the transaction will fail, leaving multiple orphaned temporary tables.
+        <para>Typically, <productname>1C</productname> solutions use a lot of temporary tables. Every backend process usually contains multiple temporary tables. When closing a connection, <productname>&productname;</productname> tries to drop all temporary tables in a single transaction, so this transaction may use a lot of locks. If the number of locks exceeds the <varname>max_locks_per_transaction</varname> value, the transaction will fail, leaving multiple orphaned temporary tables.
         </para>
       </listitem>
       </itemizedlist>

doc/src/sgml/dump-stat.sgml

@@ -13,7 +13,7 @@
         <link linkend="catalog-pg-statistic"><structname>pg_statistic</structname></link>
         table. The <function>dump_statistic</> function generates <literal>INSERT</>
         statements which can later be applied to a compatible database. The extension
-        should be installed on the recipient server in order to successfuly restore
+        should be installed on the recipient server in order to successfully restore
         statistical data since these statements heavily rely on the provided functions.
     </para>
 

doc/src/sgml/fulleq.sgml

@@ -12,7 +12,7 @@
     <para>
       The <productname>&productname;</productname> equivalence operator is
       defined to return NULL when both operands are NULLs. However, the Microsoft
-      SQL Servers family traditionaly defines other semantic for equivalence
+      SQL Servers family traditionally defines other semantic for equivalence
       operator, where operator returns TRUE in the case of both nulled operands.
       This module provides such operator with MSSQL semantic.
     </para>

doc/src/sgml/intro.sgml

@@ -286,6 +286,9 @@
         including the current wait events for all processes and background
         workers.</simpara>
     </listitem>
+    <listitem>
+     <simpara><application>pg_tsparser</application> module is an alternative text search parser.</simpara>
+    </listitem>
    </itemizedlist>
   </para>
 

doc/src/sgml/jsquery.sgml

@@ -588,7 +588,7 @@ CREATE TABLE js (
         Unfortunately, jsonb have no statistics yet. That's why JsQuery
         optimizer has to do imperative decision while selecting
         conditions to be evaluated using index. This decision is made by
-        assumtion that some condition types are less selective than
+        assumption that some condition types are less selective than
         others. Optimizer divides conditions into following selectivity
         class (listed by descending of selectivity).
       </para>

doc/src/sgml/mchar.sgml

@@ -28,7 +28,7 @@
     <itemizedlist>
     <listitem>
     <para>
-    Case insensitive comparation
+    Case insensitive comparison
     </para>
     </listitem>
     <listitem>

doc/src/sgml/pgprobackup.sgml

@@ -687,7 +687,7 @@ pg_probackup show
 
       <listitem>
        <para>
-         Time &mdash; time it took to peform the backup.
+         Time &mdash; time it took to perform the backup.
        </para>
       </listitem>
 

doc/src/sgml/pgquerystate.sgml

@@ -8,7 +8,7 @@
     <title>Overview</title>
     <para>
       Each nonutility query statement (SELECT/INSERT/UPDATE/DELETE) after
-      optimization/planning stage is translated into plan tree wich is kind of
+      optimization/planning stage is translated into plan tree, which is kind of
       imperative representation of declarative SQL query. EXPLAIN ANALYZE
       request allows to demonstrate execution statistics gathered from each
       node of plan tree (full time of execution, number of rows emitted to upper
@@ -138,7 +138,7 @@
       </listitem>
       <listitem>
         <para>
-          format - EXPLAIN format to be used for plans printing, posible values:
+          format - EXPLAIN format to be used for plans printing, possible values:
           text, xml, json, yaml.
         </para>
       </listitem>
@@ -150,7 +150,7 @@
     </para>
     <para>
       Calling role have to be superuser or member of the role whose backend is
-      being called. Othrewise function prints ERROR message
+      being called. Otherwise function prints ERROR message
       <literal>permission denied</literal>.
     </para>
   </sect2>

doc/src/sgml/ref/waitlsn.sgml

@@ -57,7 +57,7 @@ WAITLSN <replaceable class="PARAMETER">'LSN'</replaceable> [ , <replaceable clas
     <term><replaceable class="PARAMETER">delay</replaceable></term>
     <listitem>
      <para>
-      Time in miliseconds to waiting for LSN to be replayed.
+      Time to wait for LSN to be replayed, in milliseconds.
      </para>
     </listitem>
    </varlistentry>
@@ -69,7 +69,7 @@ WAITLSN <replaceable class="PARAMETER">'LSN'</replaceable> [ , <replaceable clas
 
   <para>
    Delay time to waiting for LSN to be replayed must be integer. For
-   default it is infinity. Waiting can be interupped using Ctl+C, or
+   default it is infinity. Waiting can be interrupted using Ctl+C, or
    by Postmaster death.
   </para>
  </refsect1>

doc/src/sgml/release-pro-9.6.sgml

@@ -46,10 +46,6 @@
       <listitem>
         <para>Updated PTRACK patch to version 1.2.</para>
       </listitem>
-      <listitem>
-        <para>Updated pg_probackup to version 1.1.11. Command line interface
-          has been changed.</para>
-      </listitem>
       <listitem>
         <para>Provided performance improvements for queries typical for 1C solutions.</para>
       </listitem>
@@ -341,7 +337,7 @@
         use of <xref linkend="pgupgrade">, is required for those
           wishing to migrate data from any previous release.</para>
 
-    <para>Dump/restore is not neccessary when migrating from PostgreSQL 9.6.x to
+    <para>Dump/restore is not necessary when migrating from PostgreSQL 9.6.x to
       Postgres Pro 9.6.x.y.</para>
 
     <para>When upgrading from previous releases of Postgres Pro or from

doc/src/sgml/sr_plan.sgml

@@ -20,7 +20,7 @@
     <para>
       Typically, DBA would play with queries interactively, and save
       their plans and then enable use of saved plans for the queries,
-      where predictable responce time is essential.
+      where predictable response time is essential.
     </para>
     <para>
       Then application which uses these queries would use saved plans.
@@ -136,7 +136,7 @@ SET
       <literal>_p()</> function.
     </para>
     <programlisting>
-=&gt;update sr_plans set enable = true where quesry=
+=&gt;update sr_plans set enable = true where query=
   'select a,b from test_table where a = _p(1)';
 UPDATE 1
 -- These queries would use saved plan