Merge branch 'PGPROEE10' of gitlab.postgrespro.ru:pgpro-dev/postgrespro into PGPROEE10

vbwagner · vbwagner · commit 78e0c5714544 · 2018-02-02T18:43:11.000+03:00
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
@@ -197,6 +197,7 @@
 <!ENTITY sourcerepo SYSTEM "sourcerepo.sgml">
 
 <!ENTITY release    SYSTEM "release.sgml">
+<!ENTITY release-proee-10 SYSTEM "release-proee-10.sgml">
 <!ENTITY release-pro-10 SYSTEM "release-pro-10.sgml">
 <!ENTITY release-pro-9.6 SYSTEM "release-pro-9.6.sgml">
 <!ENTITY release-pro-9.5 SYSTEM "release-pro-9.5.sgml">
diff --git a/doc/src/sgml/installation-bin.sgml b/doc/src/sgml/installation-bin.sgml
diff --git a/doc/src/sgml/intro.sgml b/doc/src/sgml/intro.sgml
@@ -289,6 +289,28 @@
     <listitem>
      <simpara><application>pg_tsparser</application> module is an alternative text search parser.</simpara>
     </listitem>
+      <listitem>
+        <simpara>
+          <filename>pg_shardman</filename> module is an experimental extension
+          that enables sharding, aiming for scalability and fault tolerance
+          with transaction support. It provides best results for
+          <acronym>OLTP</acronym> workloads.
+        </simpara>
+      </listitem>
+      <listitem>
+        <simpara>
+          <filename>in-memory</filename> module
+          enables you to store data in <productname>&productname;</productname>
+          shared memory.
+        </simpara>
+      </listitem>
+      <listitem>
+        <simpara>
+          <filename>vops</filename> module enables vertical data model
+          for &productname;. It can speed up <acronym>OLAP</acronym> queries
+          with filtering and aggregation by times.
+        </simpara>
+      </listitem>
    </itemizedlist>
   </para>
 
diff --git a/doc/src/sgml/multimaster.sgml b/doc/src/sgml/multimaster.sgml
@@ -541,76 +541,6 @@ SELECT mtm.get_cluster_state();
       <para><emphasis role="strong">See Also</emphasis></para>
       <para><link linkend="multimaster-tuning-configuration-parameters">Tuning
       Configuration Parameters</link></para>
-    <sect4>
-      <title>Sample Cluster Configuration</title>
-    <para>
-      This section shows a sample configuration of a three-node cluster for the
-      <literal>myuser</literal> user and <literal>mydb</literal> database.
-    </para>
-    <para>
-      First, run the following commands on all cluster nodes:
-      <programlisting>
-# Switch to the 'postgres' user
-sudo su - postgres
-
-# Set up environment variables
-export PGHOME=/usr/pgproee-&majorversion;
-export PATH=$PGHOME/bin:$PATH
-export MANPATH=$PGHOME/share/man:$MANPATH
-export PGDATA=/var/lib/pgproee/&majorversion;/data
-
-# Create a new user 'myuser' with superuser priviledges
-psql --dbname=postgres --username=postgres -c "CREATE USER myuser WITH SUPERUSER ENCRYPTED PASSWORD 'myuserpassword'"
-
-# Create a new database 'mydb'
-psql --dbname=postgres --username=myuser --host=127.0.0.1 -c "CREATE DATABASE mydb"
-
-# Enable replication on all cluster nodes.
-# The 'trust' method in this example is only provided for
-# illustration purposes and is not recommended on production systems.
-sed -i '/md5$/s|host|#host|' $PGDATA/pg_hba.conf
-echo "host replication myuser samenet trust" >> $PGDATA/pg_hba.conf
-echo "host all all 0.0.0.0/0 md5" >> $PGDATA/pg_hba.conf
-
-# Configure postgresql.conf settings
-echo "multimaster.max_nodes = 3" >> $PGDATA/postgresql.conf
-echo "multimaster.node_id = 'hostname | '{ print substr($1,5,1) }''" >> $PGDATA/postgresql.conf
-echo "multimaster.conn_strings = 'dbname=mydb user=myuser host=node1,dbname=mydb user=myuser host=node2,dbname=mydb user=myuser host=node3'" >> $PGDATA/postgresql.conf
-psql --dbname=mydb --username=myuser --host=127.0.0.1 -c "ALTER SYSTEM SET default_transaction_isolation TO 'read committed'"
-psql --dbname=mydb --username=myuser --host=127.0.0.1 -c "ALTER SYSTEM SET wal_level TO logical"
-psql --dbname=mydb --username=myuser --host=127.0.0.1 -c "ALTER SYSTEM SET max_connections TO 100"
-psql --dbname=mydb --username=myuser --host=127.0.0.1 -c "ALTER SYSTEM SET max_prepared_transactions to 300"
-psql --dbname=mydb --username=myuser --host=127.0.0.1 -c "ALTER SYSTEM SET max_wal_senders TO 10"
-psql --dbname=mydb --username=myuser --host=127.0.0.1 -c "ALTER SYSTEM SET max_replication_slots TO 10"
-psql --dbname=mydb --username=myuser --host=127.0.0.1 -c "ALTER SYSTEM SET max_worker_processes TO 250"
-psql --dbname=mydb --username=myuser --host=127.0.0.1 -c "ALTER SYSTEM SET shared_preload_libraries TO multimaster"
-psql --exit
-
-# Restart &productname;
-sudo systemctl restart postgrespro-enterprise-&majorversion;.service
-</programlisting>
-</para>
-  <para>
-    Now create the <filename>multimaster</filename> extension on one of the nodes.
-    It will be replicated to all the other cluster nodes automatically.
-<programlisting>
-# Switch to the 'postgres' user
-sudo su - postgres
-
-# Set up environment variables
-export PGHOME=/usr/pgproee-&majorversion;
-export PATH=$PGHOME/bin:$PATH
-export MANPATH=$PGHOME/share/man:$MANPATH
-export PGDATA=/var/lib/pgproee/&majorversion;/data
-
-# Create multimaster extension on one of the nodes
-psql --dbname=mydb --username=myuser --host=127.0.0.1 -c "CREATE EXTENSION IF NOT EXISTS multimaster"
-</programlisting>
-  </para>
-  <para>
-    The cluster is set up and ready to use.
-  </para>
-   </sect4>
   </sect3>
     <sect3 id="multimaster-tuning-configuration-parameters">
     <title>Tuning Configuration Parameters</title>
diff --git a/doc/src/sgml/plantuner.sgml b/doc/src/sgml/plantuner.sgml
@@ -1,50 +1,45 @@
 <sect1 id="plantuner">
   <title>plantuner</title>
   <para>
-    The <literal>plantuner</literal> module provides hits for planner,
-    which can disable or enable indexes for query execution.
+    The <filename>plantuner</filename> module provides hints
+    for the planner that can disable or enable indexes for query execution.
   </para>
 
   <sect2 id="plantuner-motivation">
     <title>Motivation</title>
     <para>
-      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 &productname; (and PostgreSQL).
-      Oracle, for example, has over 120 hints,
-      and Microsoft SQL Server also supports hints.
+      In some cases, it may be required to control the planner
+      by providing hints that make the optimizer ignore some
+      parts of its algorithm. There are many situations when
+      a developer may want to temporarily disable specific
+      index(es), without dropping them, or to instruct the planner to
+      use a specific index.
     </para>
     <para>
-      This first version of plantuner provides a possibility to hide
-      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 &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
-      table which hasn't blocks in a file.
+      This version of <filename>plantuner</filename> provides a
+      possibility to hide the specified indexes from &productname;
+      planner, so it will not use them. For some workloads, &productname;
+      could be too pessimistic about newly created tables and assume
+      that there are much more rows in a table than it actually has. If the
+      <varname>plantuner.fix_empty_table</varname> GUC variable is set
+      to <literal>true</literal>, <filename>plantuner</filename> sets to zero
+      the number of pages/tuples of the table that has no blocks in a file.
     </para>
   </sect2>
 
-  <sect2 id="plantuner-syntax">
-    <title>Syntax</title>
-    <para>plantuner.disable_index &mdash; List of indexes invisible to planner</para>
-    <para>plantuner.enable_index &mdash; List of indexes visible to planner even they are hidden by plantuner.disable_index.</para>
+  <sect2 id="plantuner-guc-variables">
+    <title>GUC Variables</title>
+    <para><varname>plantuner.disable_index</varname> &mdash; list of indexes invisible to planner.</para>
+    <para><varname>plantuner.enable_index</varname> &mdash; list of indexes visible to planner even if they are hidden by <varname>plantuner.disable_index</varname>.</para>
   </sect2>
 
   <sect2 id="plantuner-usage-example">
     <title>Example</title>
     <para>
-      To enable the module you can either load shared library 'plantuner' in
-      psql session or specify 'shared_preload_libraries' option in
-      postgresql.conf.
+      To enable the module, you can either load <literal>plantuner</literal>
+      shared library in a <literal>psql</literal> session or specify
+      <varname>shared_preload_libraries</varname> option in
+      <filename>postgresql.conf</filename>.
       <programlisting>
 =# LOAD 'plantuner';
 =# create table test(id int);
diff --git a/doc/src/sgml/ref/pg-setup.sgml b/doc/src/sgml/ref/pg-setup.sgml
@@ -56,12 +56,12 @@
   <application>pg-setup</application> is a shell script provided in
   the <productname>&productname;</productname> distribution to automate
   database cluster setup on Linux systems. This script is provided as
-  part of the <filename>postgrespro-std-&majorversion;-server</filename>
+  part of the <filename>postgrespro-&edition;-&majorversion;-server</filename>
   package. Once <productname>&productname;</productname> is installed,
   you can find <application>pg-setup</application>
   in the <filename><replaceable>install-dir</replaceable>/bin</filename>
   directory, where <replaceable>install-dir</replaceable> is
-  <filename>/opt/pgpro/std-&majorversion;</filename>.
+  <filename>/opt/pgpro/&edition;-&majorversion;</filename>.
  </para>
  <para>
   <application>pg-setup</application> must be run as root, but performs database
@@ -104,24 +104,28 @@
      <varlistentry>
       <term><option>initdb [<replaceable>initdb_options</replaceable>]</option></term>
       <listitem><para>Initialize the database cluster on behalf of the
-      <literal>postgres</literal> user. Optionally, you can provide
-      any <xref linkend="app-initdb"> options to customize the installation.
+      <literal>postgres</literal> user.
       </para>
-      <para>If no <application>initdb</application>
-      options are provided, the database cluster is initialized in the
-      <filename>/var/lib/pgpro/std-&majorversion;/data</filename> directory,
-      using localization settings specified in the <envar>LANG</envar>
+      <para>By default, the database cluster is initialized in the
+      <filename>/var/lib/pgpro/&edition;-&majorversion;/data</filename> directory,
+      with checksums enabled, <literal>auth-local</literal> parameter
+      set to <literal>peer</literal>, and <literal>auth-host</literal>
+      parameter set to <literal>md5</literal>.
+      Localization settings are inherited from the <envar>LANG</envar>
       environment variable for the current session.
       All the <literal>LC_*</literal> environment variables are ignored.
+      Optionally, you can provide <xref linkend="app-initdb"> options
+      to customize the installation.
       </para>
-      <note>
+      <important>
       <para>
-      <application>pg-setup</application> initializes the database cluster
-      with checksums enabled. If this is not what you expect, do not
+      With <application>pg-setup</application>, you cannot
+      initialize the database cluster with checksums disabled or
+      choose the data directory. If this is not what you expect, do not
       use <application>pg-setup</application> for cluster initialization
       and run <xref linkend="app-initdb"> directly instead.
       </para>
-      </note>
+      </important>
       </listitem>
      </varlistentry>
 
@@ -198,17 +202,17 @@
   <title>Notes</title>
   <para>
     If you are installing <productname>&productname;</productname>
-    from the <filename>postgrespro-std-&majorversion;</filename> package,
+    from the <filename>postgrespro-&edition;-&majorversion;</filename> package,
     <application>pg-setup</application> is invoked automatically with the default settings.
     As a result, the database cluster is initialized and the
     default database is created in the
-    <filename>/var/lib/pgpro/std-&majorversion;/data</filename> directory,
+    <filename>/var/lib/pgpro/&edition;-&majorversion;/data</filename> directory,
     <productname>&productname;</productname> service autostart is enabled,
     and the service is started.
   </para>
   <para>
     If you are installing <productname>&productname;</productname> server
-    directly from the <filename>postgrespro-std-&majorversion;-server</filename>
+    directly from the <filename>postgrespro-&edition;-&majorversion;-server</filename>
     package, you can run this script manually to initialize the database cluster
     or manage the <productname>&productname;</productname> service.
   </para>
diff --git a/doc/src/sgml/ref/pg-wrapper.sgml b/doc/src/sgml/ref/pg-wrapper.sgml
@@ -41,21 +41,21 @@
   provided programs and adjust the handling of
   <acronym>SQL</acronym> man pages on Linux systems.
   Since <productname>&productname;</productname> is installed into
-  <filename>/opt/pgpro/std-&majorversion;</filename>, this is required to make
+  <filename>/opt/pgpro/&edition;-&majorversion;</filename>, this is required to make
   client and server programs available in the standard system
   <envar>PATH</envar> and find the new <acronym>SQL</acronym> man pages.
   This setup is not performed automatically at installation time to avoid possible conflicts
   with other <productname>PostgreSQL</productname>-based products
   you may have installed, unless you have opted for using the
-  <filename>postgrespro-std-&majorversion;</filename> quick-install package.
+  <filename>postgrespro-&edition;-&majorversion;</filename> quick-install package.
  </para>
  <para>
   <application>pg-wrapper</application> is provided as part of the
-  <filename>postgrespro-std-&majorversion;-client</filename> package.
+  <filename>postgrespro-&edition;-&majorversion;-client</filename> package.
   Once this package is installed, you can find <application>pg-wrapper</application>
   in the <filename><replaceable>install-dir</replaceable>/bin</filename>
   directory, where <replaceable>install-dir</replaceable> is
-  <filename>/opt/pgpro/std-&majorversion;</filename>.
+  <filename>/opt/pgpro/&edition;-&majorversion;</filename>.
  </para>
  <para>
   <application>pg-wrapper</application> must be run as root.
@@ -105,7 +105,7 @@
   <title>Notes</title>
   <para>
     If you are installing <productname>&productname;</productname>
-    from the <filename>postgrespro-std-&majorversion;</filename> package,
+    from the <filename>postgrespro-&edition;-&majorversion;</filename> package,
     <application>pg-wrapper</application> is invoked automatically.
   </para>
   <para>
diff --git a/doc/src/sgml/release-proee-10.sgml b/doc/src/sgml/release-proee-10.sgml
diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
