From a0a2f87d3292976e570cec56449a9ee75c5f043f Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Thu, 12 Mar 2015 10:50:02 +0900 Subject: [PATCH] Fix format and typos --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 4576a2fe..49b2ac79 100644 --- a/README.md +++ b/README.md @@ -20,8 +20,8 @@ versions please continue use the 2.x branch. New features in `repmgr 3` include: -* use pg_basebackup to clone servers -* supportsfor timeline following, meaning a standby does not have to be +* using `pg_basebackup` to clone servers +* support for timeline following, meaning a standby does not have to be restarted after being promoted to master * support for cascading replication * support for tablespace remapping (in PostgreSQL 9.3 via rsync only) @@ -105,12 +105,12 @@ settings: wal_keep_segments = 5000 # in logfile segments, 16MB each; 0 disables hot_standby = on # "on" allows queries during recovery -Note that `repmgr` expects a default of 5000 wal_keep_segments, although this +Note that `repmgr` expects a default of 5000 `wal_keep_segments`, although this value can be overridden when executing the `repmgr` client. From PostgreSQL 9.4, replication slots are available, which remove the requirement to retain a fixed number of WAL logfile segments. See -'repmgr configuration' for details. +"repmgr configuration" for details. Additionally, `repmgr` requires a dedicated PostgreSQL superuser account and a database in which to store monitoring and replication data. The `repmgr`