mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-27 17:06:29 +00:00
Events table removed for now
Was very experimental.
This commit is contained in:
9
FAQ.md
9
FAQ.md
@@ -26,13 +26,10 @@ General
|
|||||||
(However this does mean that if a standby is no longer connected to the
|
(However this does mean that if a standby is no longer connected to the
|
||||||
master, the master will retain WAL files indefinitely).
|
master, the master will retain WAL files indefinitely).
|
||||||
|
|
||||||
- What's the difference between the `repl_status` view and `repl_events`
|
- How many replication slots should I define in `max_replication_slots`?
|
||||||
table?
|
|
||||||
|
...
|
||||||
|
|
||||||
The `repl_status` view shows the latest node status as reported by
|
|
||||||
`repmgrd` and is useful for monitoring current lag.
|
|
||||||
`repl_events` is a record of significant events which have
|
|
||||||
taken place, such as a node being registered or a failover event.
|
|
||||||
|
|
||||||
`repmgr`
|
`repmgr`
|
||||||
--------
|
--------
|
||||||
|
|||||||
Reference in New Issue
Block a user