diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/high-availability.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/ref/pg_receivexlog.sgml | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 9d43586fe2f..a526f6d5b12 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -756,7 +756,7 @@ archive_cleanup_command = 'pg_archivecleanup /path/to/archive %r' has received them. If this occurs, the standby will need to be reinitialized from a new base backup. You can avoid this by setting <varname>wal_keep_segments</> to a value large enough to ensure that - WAL segments are not recycled too early, or by configuration a replication + WAL segments are not recycled too early, or by configuring a replication slot for the standby. If you set up a WAL archive that's accessible from the standby, these solutions are not required, since the standby can always use the archive to catch up provided it retains enough segments. diff --git a/doc/src/sgml/ref/pg_receivexlog.sgml b/doc/src/sgml/ref/pg_receivexlog.sgml index 2a44af46c52..f05e7180948 100644 --- a/doc/src/sgml/ref/pg_receivexlog.sgml +++ b/doc/src/sgml/ref/pg_receivexlog.sgml @@ -235,7 +235,7 @@ PostgreSQL documentation When this option is used, <application>pg_receivexlog</> will report a flush position to the server, indicating when each segment has been synchronized to disk so that the server can remove that segment if it - is not otherwise needed. When using this paramter, it is important + is not otherwise needed. When using this parameter, it is important to make sure that <application>pg_receivexlog</> cannot become the synchronous standby through an incautious setting of <xref linkend="guc-synchronous-standby-names">; it does not flush |