github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-24 07:36:30 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

Merge pull request #31 from riegie/patch-1

Browse Source 
Update README.rst
This commit is contained in:
Abhijit Menon-Sen
2014-06-26 22:51:52 +05:30
parent 5b15fcff5c 0b5b3aaa4b
commit 8f47111072
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.rst
View File

@@ -77,7 +77,7 @@ and run::
And if a previously failed node becomes available again, such as
the lost node1 above, you can get it to resynchronize by only copying
over changes made while it was down using. That hapens with what's
over changes made while it was down using. That happens with what's
called a forced clone, which overwrites existing data rather than
assuming it starts with an empty database directory tree::