diff --git a/doc/src/sgml/appendix-obsolete-pgreceivexlog.sgml b/doc/src/sgml/appendix-obsolete-pgreceivexlog.sgml
new file mode 100644
index 00000000000..f74d0ae832e
--- /dev/null
+++ b/doc/src/sgml/appendix-obsolete-pgreceivexlog.sgml
@@ -0,0 +1,24 @@
+
+
+
+
+ <command>pg_receivexlog</command> renamed to <command>pg_receivewal</command>
+
+
+ pg_receivexlog
+ pg_receivewal
+
+
+
+ PostgreSQL 9.6 and below provided a command named
+ pg_receivexlog
+ pg_receivexlog
+ to fetch write-ahead-log (WAL) files. This command was renamed to pg_receivewal, see
+ for documentation of pg_receivewal and see
+ the release notes for PostgreSQL 10 for details
+ on this change.
+
+
+
diff --git a/doc/src/sgml/appendix-obsolete-pgresetxlog.sgml b/doc/src/sgml/appendix-obsolete-pgresetxlog.sgml
new file mode 100644
index 00000000000..7d999301f15
--- /dev/null
+++ b/doc/src/sgml/appendix-obsolete-pgresetxlog.sgml
@@ -0,0 +1,24 @@
+
+
+
+
+ <command>pg_resetxlog</command> renamed to <command>pg_resetwal</command>
+
+
+ pg_resetxlog
+ pg_resetwal
+
+
+
+ PostgreSQL 9.6 and below provided a command named
+ pg_resetxlog
+ pg_resetxlog
+ to reset the write-ahead-log (WAL) files. This command was renamed to pg_resetwal, see
+ for documentation of pg_resetwal and see
+ the release notes for PostgreSQL 10 for details
+ on this change.
+
+
+
diff --git a/doc/src/sgml/appendix-obsolete-pgxlogdump.sgml b/doc/src/sgml/appendix-obsolete-pgxlogdump.sgml
new file mode 100644
index 00000000000..4173fee0414
--- /dev/null
+++ b/doc/src/sgml/appendix-obsolete-pgxlogdump.sgml
@@ -0,0 +1,24 @@
+
+
+
+
+ <command>pg_xlogdump</command> renamed to <command>pg_waldump</command>
+
+
+ pg_xlogdump
+ pg_waldump
+
+
+
+ PostgreSQL 9.6 and below provided a command named
+ pg_xlogdump
+ pg_xlogdump
+ to read write-ahead-log (WAL) files. This command was renamed to pg_waldump, see
+ for documentation of pg_waldump and see
+ the release notes for PostgreSQL 10 for details
+ on this change.
+
+
+
diff --git a/doc/src/sgml/appendix-obsolete-recovery-config.sgml b/doc/src/sgml/appendix-obsolete-recovery-config.sgml
new file mode 100644
index 00000000000..77c4289531b
--- /dev/null
+++ b/doc/src/sgml/appendix-obsolete-recovery-config.sgml
@@ -0,0 +1,58 @@
+
+
+
+
+ <filename>recovery.conf</filename> file merged into <filename>postgresql.conf</filename>
+
+
+ recovery.conf
+
+
+
+ PostgreSQL 11 and below used a configuration file named
+ recovery.conf
+ recovery.conf
+ to manage replicas and standbys. Support for this file was removed in PostgreSQL 12. See
+ the release notes for PostgreSQL 12 for details
+ on this change.
+
+
+
+ On PostgreSQL 12 and above,
+ archive recovery, streaming replication, and PITR
+ are configured using
+ normal server configuration parameters.
+ These are set in postgresql.conf or via
+ ALTER SYSTEM
+ like any other parameter.
+
+
+
+ The server will not start if a recovery.conf exists.
+
+
+
+ The
+ trigger_file
+
+ trigger_file
+ promote_trigger_file
+
+ setting has been renamed to
+ .
+
+
+
+ The
+ standby_mode
+
+ standby_mode
+ standby.signal
+
+ setting has been removed. A standby.signal file in the data directory
+ is used instead. See for details.
+
+
+
diff --git a/doc/src/sgml/appendix-obsolete.sgml b/doc/src/sgml/appendix-obsolete.sgml
new file mode 100644
index 00000000000..ffd7d40263e
--- /dev/null
+++ b/doc/src/sgml/appendix-obsolete.sgml
@@ -0,0 +1,41 @@
+
+
+
+ Obsolete or Renamed Features
+
+
+ Functionality is sometimes removed from PostgreSQL, feature, setting
+ and file names sometimes change, or documentation moves to different
+ places. This section directs users coming from old versions of the
+ documentation or from external links to the appropriate new location
+ for the information they need.
+
+
+
+
+ &obsolete-recovery-config;
+ &obsolete-pgxlogdump;
+ &obsolete-pgresetxlog;
+ &obsolete-pgreceivexlog;
+
+
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index da323621b53..3cb7d04ef79 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -4062,8 +4062,9 @@ ANY num_sync ( standby server
+ that is to receive replication data. Their values on the master server
are irrelevant.
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index 8960f112786..332cb4a7d15 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -179,3 +179,10 @@
+
+
+
+
+
+
+
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 07d3982c306..22ac33bda30 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -611,9 +611,17 @@ protocol to make nodes agree on a serializable transactional order.
-
+ Standby Server Operation
+
+ A server enters standby mode if a
+
+ standby.signal
+ standby.signal
+ file exists in the data directory when the server is started.
+
+
In standby mode, the server continuously applies WAL received from the
master server. The standby server can read WAL from a WAL archive
@@ -686,7 +694,8 @@ protocol to make nodes agree on a serializable transactional order.
To set up the standby server, restore the base backup taken from primary
server (see ). Create a file
- standby.signal in the standby's cluster data
+ standby.signalstandby.signal
+ in the standby's cluster data
directory. Set to a simple command to copy files from
the WAL archive. If you plan to have multiple standby servers for high
availability purposes, make sure that recovery_target_timeline is set to
@@ -2103,7 +2112,8 @@ if (!triggered)
If hot_standby is on in postgresql.conf
- (the default value) and there is a standby.signal
+ (the default value) and there is a
+ standby.signalstandby.signalfor hot standby
file present, the server will run in Hot Standby mode.
However, it may take some time for Hot Standby connections to be allowed,
because the server will not accept connections until it has completed
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index 3e115f1c76c..25d8f2204b2 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -278,6 +278,7 @@
&docguide;
&limits;
&acronyms;
+ &obsolete;
diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml
index 01dac102571..fde143c763a 100644
--- a/doc/src/sgml/ref/pg_basebackup.sgml
+++ b/doc/src/sgml/ref/pg_basebackup.sgml
@@ -215,7 +215,9 @@ PostgreSQL documentation
- Create standby.signal and append connection settings
+ Create standby.signal
+ standby.signalpg_basebackup --write-recovery-conf
+ file and append connection settings
to postgresql.auto.conf in the output
directory (or into the base archive file when using tar format) to
ease setting up a standby server.