[DOC] [PGPRO-7104] Remove outdated options and PostgreSQL versions from documentation [skip travis]

Author: indrups

doc/pgprobackup.xml

@@ -164,7 +164,7 @@ doc/src/sgml/pgprobackup.sgml
    recovery of <productname>PostgreSQL</productname> database clusters.
    It is designed to perform periodic backups of the <productname>PostgreSQL</productname> 
    instance that enable you to restore the server in case of a failure.
-   <application>pg_probackup</application> supports PostgreSQL 9.5 or higher.
+   <application>pg_probackup</application> supports PostgreSQL 10 or higher.
   </para>
 
 <itemizedlist spacing="compact">
@@ -416,7 +416,7 @@ doc/src/sgml/pgprobackup.sgml
       </listitem>
       <listitem>
         <para>
-          On Unix systems, for <productname>PostgreSQL</productname> 10 or lower,
+          On Unix systems, for <productname>PostgreSQL</productname> 10,
           a backup can be made only by the same OS user that has started the <productname>PostgreSQL</productname>
           server. For example, if <productname>PostgreSQL</productname> server is started by
           user <literal>postgres</literal>, the <literal>backup</literal> command must also be run
@@ -821,49 +821,6 @@ pg_probackup add-instance -B <replaceable>backup_dir</replaceable> -D <replaceab
       only in the database <emphasis role="strong">used for
       connection</emphasis> to the <productname>PostgreSQL</productname> server:
     </para>
-    <para>
-      For <productname>PostgreSQL</productname> 9.5:
-    </para>
-    <programlisting>
-BEGIN;
-CREATE ROLE backup WITH LOGIN;
-GRANT USAGE ON SCHEMA pg_catalog TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.current_setting(text) TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.set_config(text, text, boolean) TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.pg_is_in_recovery() TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.pg_start_backup(text, boolean) TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.pg_stop_backup() TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.pg_create_restore_point(text) TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.pg_switch_xlog() TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.txid_current() TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.txid_current_snapshot() TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.txid_snapshot_xmax(txid_snapshot) TO backup;
-COMMIT;
-</programlisting>
-    <para>
-      For <productname>PostgreSQL</productname> 9.6:
-    </para>
-    <programlisting>
-BEGIN;
-CREATE ROLE backup WITH LOGIN;
-GRANT USAGE ON SCHEMA pg_catalog TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.current_setting(text) TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.set_config(text, text, boolean) TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.pg_is_in_recovery() TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.pg_start_backup(text, boolean, boolean) TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.pg_stop_backup(boolean) TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.pg_create_restore_point(text) TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.pg_switch_xlog() TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.pg_last_xlog_replay_location() TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.txid_current() TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.txid_current_snapshot() TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.txid_snapshot_xmax(txid_snapshot) TO backup;
-GRANT EXECUTE ON FUNCTION pg_catalog.pg_control_checkpoint() TO backup;
-COMMIT;
-</programlisting>
-    <para>
-      For <productname>PostgreSQL</productname> versions 10 &mdash; 14:
-    </para>
     <programlisting>
 BEGIN;
 CREATE ROLE backup WITH LOGIN;
@@ -1110,7 +1067,7 @@ archive_command = '"<replaceable>install_dir</replaceable>/pg_probackup" archive
   <refsect2 id="pbk-setting-up-backup-from-standby">
     <title>Setting up Backup from Standby</title>
     <para>
-      For <productname>PostgreSQL</productname> 9.6 or higher, <application>pg_probackup</application> can take backups from
+      <application>pg_probackup</application> can take backups from
       a standby server. This requires the following additional setup:
     </para>
     <itemizedlist spacing="compact">
@@ -5013,8 +4970,7 @@ pg_probackup catchup -b <replaceable>catchup_mode</replaceable>
       <listitem>
       <para>
         Specifies the LSN of the write-ahead log location up to which
-        recovery will proceed. Can be used only when restoring
-        a database cluster of major version 10 or higher.
+        recovery will proceed.
       </para>
       </listitem>
       </varlistentry>
@@ -5976,124 +5932,6 @@ pg_probackup catchup -b <replaceable>catchup_mode</replaceable>
       </variablelist>
       </para>
     </refsect3>
-    <refsect3 id="pbk-replica-options">
-      <title>Replica Options</title>
-      <para>
-        This section describes the options related to taking a backup
-        from standby.
-      </para>
-      <note>
-        <para>
-          Starting from <application>pg_probackup</application> 2.0.24, backups can be
-          taken from standby without connecting to the master server,
-          so these options are no longer required. In lower versions,
-          <application>pg_probackup</application> had to connect to the master to determine
-          recovery time — the earliest moment for which you can
-          restore a consistent state of the database cluster.
-        </para>
-      </note>
-      <para>
-      <variablelist>
-      <varlistentry>
-<term><option>--master-db=<replaceable>dbname</replaceable></option></term>
-      <listitem>
-      <para>
-        Deprecated. Specifies the name of the database on the master
-        server to connect to. The connection is used only for managing
-        the backup process, so you can connect to any existing
-        database. Can be set in the <filename>pg_probackup.conf</filename> using the
-        <xref linkend="pbk-set-config"/> command.
-      </para>
-      <para>
-       Default: <literal>postgres</literal>, the default <productname>PostgreSQL</productname> database
-      </para>
-      </listitem>
-      </varlistentry>
-
-      <varlistentry>
-<term><option>--master-host=<replaceable>host</replaceable></option></term>
-      <listitem>
-      <para>
-        Deprecated. Specifies the host name of the system on which the
-        master server is running.
-      </para>
-      </listitem>
-      </varlistentry>
-
-      <varlistentry>
-<term><option>--master-port=<replaceable>port</replaceable></option></term>
-      <listitem>
-      <para>
-        Deprecated. Specifies the TCP port or the local Unix domain
-        socket file extension on which the master server is listening
-        for connections.
-      </para>
-      <para>
-       Default: <literal>5432</literal>, the <productname>PostgreSQL</productname> default port
-      </para>
-      </listitem>
-      </varlistentry>
-
-      <varlistentry>
-<term><option>--master-user=<replaceable>username</replaceable></option></term>
-      <listitem>
-      <para>
-        Deprecated. User name to connect as.
-      </para>
-      <para>
-       Default: <literal>postgres</literal>,
-       the <productname>PostgreSQL</productname> default user name
-      </para>
-      </listitem>
-      </varlistentry>
-
-      <varlistentry>
-<term><option>--replica-timeout=<replaceable>timeout</replaceable></option></term>
-<term><option></option></term>
-      <listitem>
-      <para>
-        Deprecated. Wait time for WAL segment streaming via
-        replication, in seconds. By default, <application>pg_probackup</application> waits 300
-        seconds. You can also define this parameter in the
-        <filename>pg_probackup.conf</filename> configuration file using the
-        <xref linkend="pbk-set-config"/> command.
-      </para>
-      <para>
-       Default: <literal>300 sec</literal>
-      </para>
-      </listitem>
-      </varlistentry>
-      </variablelist>
-      </para>
-    </refsect3>
-
-    <refsect3 id="pbk-test-options">
-      <title>Testing and Debugging Options</title>
-      <para>
-        This section describes options useful only in a test or development environment.
-      </para>
-      <para>
-        <variablelist>
-          <varlistentry>
-          <term><option>--destroy-all-other-dbs</option></term>
-          <listitem>
-            <para>
-              By default, <application>pg_probackup</application> exits with an
-              error if an attempt is made to perform a partial incremental restore
-              since this destroys databases not included in the restore set. This
-              flag allows you to suppress the error and proceed with the partial
-              incremental restore (e.g., to keep a development database snapshot
-              up-to-date with a production one). This option can be used with the
-              <xref linkend="pbk-restore"/> command.
-            </para>
-            <important>
-              <para>Never use this flag in a production cluster.</para>
-            </important>
-          </listitem>
-          </varlistentry>
-        </variablelist>
-      </para>
-    </refsect3>
  </refsect2>
  </refsect1>
 
@@ -6305,8 +6143,6 @@ xlog-seg-size = 16777216
 pgdatabase = backupdb
 pghost = postgres_host
 pguser = backup
-# Replica parameters
-replica-timeout = 5min
 # Archive parameters
 archive-timeout = 5min
 # Logging parameters