From b152cccd69e062d1507211bbf021e32de2259092 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Wed, 11 Mar 2015 21:26:43 +0900 Subject: [PATCH] Events table removed for now Was very experimental. --- FAQ.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/FAQ.md b/FAQ.md index aa3d59a3..677ab5e0 100644 --- a/FAQ.md +++ b/FAQ.md @@ -26,13 +26,10 @@ General (However this does mean that if a standby is no longer connected to the master, the master will retain WAL files indefinitely). -- What's the difference between the `repl_status` view and `repl_events` - table? +- How many replication slots should I define in `max_replication_slots`? + + ... - 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` --------