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

Clarify repmgr database role

Browse Source
This commit is contained in:
Ian Barwick
2014-07-16 14:10:18 +09:00
parent 253992c5ec
commit 313d787ebf
1 changed files with 12 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
QUICKSTART.md
View File

@@ -82,9 +82,12 @@ Note that repmgr expects a default of 5000 wal_keep_segments, although this
value can be overridden when executing the `repmgr` client. value can be overridden when executing the `repmgr` client.
Additionally, repmgr requires a dedicated PostgreSQL superuser account Additionally, repmgr requires a dedicated PostgreSQL superuser account
and a database in which to store monitoring and replication data. The and a database in which to store monitoring and replication data. The repmgr
database can in principle be any database, including the default postgres user account will also be used for replication connections from the standby,
one, however it's probably advisable to create a dedicated repmgr database. so a seperate replication user with the `REPLICATION` privilege is not required.
The database can in principle be any database, including the default `postgres`
one, however it's probably advisable to create a dedicated database for repmgr
usage.
### repmgr configuration ### repmgr configuration
@@ -144,7 +147,7 @@ Master setup
``` ```
host repmgr_db repmgr_usr 192.168.1.0/24 trust host repmgr_db repmgr_usr 192.168.1.0/24 trust
host replication repuser 192.168.1.0/24 trust host replication repmgr_usr 192.168.1.0/24 trust
``` ```
Restart the PostgreSQL server after making these changes. Restart the PostgreSQL server after making these changes.
@@ -171,7 +174,7 @@ Slave/standby setup
1. Use repmgr to clone the master: 1. Use repmgr to clone the master:
$ repmgr -f $HOME/repmgr/repmgr.conf -D $PGDATA -d repmgr_db -U repmgr_usr -R postgres --verbose standby clone 192.168.1.2 $ repmgr -D $PGDATA -d repmgr_db -U repmgr_usr -R postgres --verbose standby clone 192.168.1.2
Opening configuration file: ./repmgr.conf Opening configuration file: ./repmgr.conf
[2014-07-04 10:49:00] [ERROR] Did not find the configuration file './repmgr.conf', continuing [2014-07-04 10:49:00] [ERROR] Did not find the configuration file './repmgr.conf', continuing
[2014-07-04 10:49:00] [INFO] repmgr connecting to master database [2014-07-04 10:49:00] [INFO] repmgr connecting to master database
@@ -190,8 +193,10 @@ Slave/standby setup
-R is the database system user on the master node. At this point it does not matter -R is the database system user on the master node. At this point it does not matter
if the `repmgr.conf` file is not found. if the `repmgr.conf` file is not found.
This will clone the PostgreSQL database files from the master, and additionally This will clone the PostgreSQL database files from the master, including its
create an appropriate `recovery.conf` file. `postgresql.conf` and `pg_hba.conf` files, and additionally automatically create
the `recovery.conf` file containing the correct parameters to start streaming
from the primary node.
2. Start the PostgreSQL server 2. Start the PostgreSQL server