Documentation updates

This commit is contained in:
Ian Barwick
2017-06-22 15:28:31 +09:00
parent 0ffd33820c
commit 9ce981c9f8
2 changed files with 29 additions and 4 deletions

View File

@@ -9,6 +9,18 @@ operations.
`repmgr 4` is a complete rewrite of the existing `repmgr` codebase. `repmgr 4` is a complete rewrite of the existing `repmgr` codebase.
Supports PostgreSQL 9.3 and later.
Building from source
--------------------
Simply:
./configure && make install
Ensure `pg_config` for the target PostgreSQL version is in `$PATH`.
Commands Commands
-------- --------
@@ -29,7 +41,10 @@ Currently available:
Backwards compatibility Backwards compatibility
----------------------- -----------------------
`repmgr` is now implemented as a PostgreSQL extension. See also: doc/changes-in-repmgr4.md
`repmgr` is now implemented as a PostgreSQL extension. NOTE: no need to
install the extension, this will be done automatically by `repmgr master register`.
Metadata tables have been revised and are not backwards-compatible Metadata tables have been revised and are not backwards-compatible
with 3.x. (however future DDL updates will be easier as they can be with 3.x. (however future DDL updates will be easier as they can be

View File

@@ -2,13 +2,23 @@
New command line options New command line options
------------------------ ------------------------
- --dry-run: repmgr will attempt to perform the action as far as possible - `--dry-run`: repmgr will attempt to perform the action as far as possible
without making any changes to the database without making any changes to the database
Changed command line options Changed command line options
---------------------------- ----------------------------
- --replication-user is now passed when registering the master server (and
### repmgr
- `--replication-user` is now passed when registering the master server (and
optionally when registering a standby), *not* during standby clone/follow. optionally when registering a standby), *not* during standby clone/follow.
The value (defaults to the user in the conninfo string) will be stored in The value (defaults to the user in the conninfo string) will be stored in
the repmgr metadata for use by standby clone/follow.. the repmgr metadata for use by standby clone/follow..
### repmgrd
- `--monitoring-history` is deprecated and has been replaced by the
configuration file option `monitoring_history`. This enables the
setting to be changed without having to modify system service files.