From 6b223698c9dc3028f01d04da66d930c44e372b4a Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian@2ndquadrant.com>
Date: Thu, 4 Jan 2018 21:03:36 +0900
Subject: [PATCH] Fix call to is_active_bdr_node() in BDR repmgrd

Following the fix to "is_active_bdr_node()" in 841f03ae, it turns out
the call in repmgrd-bdr.c was only accidentally working; explicitly
test for a false return value.
---
 repmgrd-bdr.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/repmgrd-bdr.c b/repmgrd-bdr.c
index 7cebaf0b..038ecb12 100644
--- a/repmgrd-bdr.c
+++ b/repmgrd-bdr.c
@@ -124,9 +124,9 @@ monitor_bdr(void)
 		exit(ERR_BAD_CONFIG);
 	}
 
-	if (is_active_bdr_node(local_conn, local_node_info.node_name))
+	if (is_active_bdr_node(local_conn, local_node_info.node_name) == false)
 	{
-		log_error(_("BDR node %s is not active, terminating"),
+		log_error(_("BDR node \"%s\" is not active, terminating"),
 				  local_node_info.node_name);
 		PQfinish(local_conn);
 		exit(ERR_BAD_CONFIG);