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

Update README

Browse Source
This commit is contained in:
Ian Barwick
2017-07-27 18:12:29 +09:00
parent 5606434a97
commit 0037d58dae
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -243,6 +243,8 @@ and registered:
2 | standby_register | t | 2016-01-08 15:04:50.621292+09 | 2 | standby_register | t | 2016-01-08 15:04:50.621292+09 |
(3 rows) (3 rows)
Alternatively use `repmgr cluster event` to output a list of events.
Additionally, event notifications can be passed to a user-defined program Additionally, event notifications can be passed to a user-defined program
or script which can take further action, e.g. send email notifications. or script which can take further action, e.g. send email notifications.
This is done by setting the `event_notification_command` parameter in This is done by setting the `event_notification_command` parameter in
@@ -294,6 +296,6 @@ The following event types are available:
* `bdr_unregister` * `bdr_unregister`
Note that under some circumstances (e.g. no replication cluster master could Note that under some circumstances (e.g. no replication cluster master could
be located), it will not be possible to write an entry into the `repl_events` be located), it will not be possible to write an entry into the `repmgr.events`
table, in which case executing a script via `event_notification_command` can table, in which case executing a script via `event_notification_command` can
serve as a fallback by generating some form of notification. serve as a fallback by generating some form of notification.