github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-26 16:46:28 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

Cleanup ReST code in README so PDF builds work

Browse Source
This commit is contained in:
Greg Smith
2010-10-30 16:41:55 -04:00
parent a0bd377f0f
commit 2082a6acd4
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
README.rst
View File

@@ -254,8 +254,8 @@ is a sample of changes to the postgresql.conf file::
listen_addresses='*' listen_addresses='*'
wal_level = 'hot_standby' wal_level = 'hot_standby'
archive_mode = on archive_mode = on
archive_command = 'cd .' # we can also use exit 0, anything that just do archive_command = 'cd .' # we can also use exit 0, anything that
# nothing # just does nothing
max_wal_senders = 10 max_wal_senders = 10
wal_keep_segments = 5000 # 80 GB required on pg_xlog wal_keep_segments = 5000 # 80 GB required on pg_xlog
hot_standby = on hot_standby = on
@@ -268,7 +268,7 @@ replication users from all internal addresses, such as::
host replication all 192.168.1.0/24 trust host replication all 192.168.1.0/24 trust
A more secure setup adds a repmgr user and database, just giving A more secure setup adds a repmgr user and database, just giving
access to that user: access to that user::
host repmgr repmgr 192.168.1.0/24 trust host repmgr repmgr 192.168.1.0/24 trust
host replication all 192.168.1.0/24 trust host replication all 192.168.1.0/24 trust
@@ -297,7 +297,8 @@ Which makes node2 the new master. We then run on node3::
To make node3 follow node2 (rather than node1) To make node3 follow node2 (rather than node1)
If now we want to add a new node we can a prepare a new server (node4) and run:: If now we want to add a new node we can a prepare a new server (node4)
and run::
repmgr -D /var/lib/postgresql/9.0 standby clone node2 repmgr -D /var/lib/postgresql/9.0 standby clone node2