github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-25 08:06:29 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

Documentation tweaks

Browse Source
This commit is contained in:
Ian Barwick
2015-05-12 10:16:52 +09:00
parent 7ad9a2c28a
commit a54478a045
2 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
QUICKSTART.md
View File

@@ -21,7 +21,8 @@ Master setup
CREATE DATABASE repmgr_db OWNER repmgr_usr; CREATE DATABASE repmgr_db OWNER repmgr_usr;
``` ```
- configure `postgresql.conf` for replication (see above) - configure `postgresql.conf` for replication (see README.md for sample
settings)
- update `pg_hba.conf`, e.g.: - update `pg_hba.conf`, e.g.:

6
README.md
View File

@@ -98,8 +98,8 @@ for details.
### PostgreSQL configuration ### PostgreSQL configuration
The primary server needs to be configured for replication with the The primary server needs to be configured for replication with settings
following settings in `postgresql.conf`: like the followingin `postgresql.conf`:
# Allow read-only queries on standby servers. The number of WAL # Allow read-only queries on standby servers. The number of WAL
# senders should be larger than the number of standby servers. # senders should be larger than the number of standby servers.
@@ -121,8 +121,6 @@ following settings in `postgresql.conf`:
archive_mode = on archive_mode = on
archive_command = 'cd .' archive_command = 'cd .'
# You can also set additional replication parameters here, such as
# hot_standby_feedback or synchronous_standby_names.
PostgreSQL 9.4 makes it possible to use replication slots, which means PostgreSQL 9.4 makes it possible to use replication slots, which means
the value of wal_keep_segments need no longer be set. With 9.3, `repmgr` the value of wal_keep_segments need no longer be set. With 9.3, `repmgr`