Avoid flooding logs if system_user is not postgres

Report and patch by TBP2k18 on github close ClusterLabs#137
ramazanebci · Jan 22, 2019 · bc6206f · bc6206f
1 parent 908f098
commit bc6206f
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -9,7 +9,8 @@ This is a bugfix release with no new features.
 
 * fix: Fix checking for notify=true, YanChii
 * fix: forbid pg_isready to timeout before the action itself, ioguix
-* misc: Avoid flooding log files with warning about non used nodes, suggested by timdeluxe on github
+* misc: avoid flooding log files when system_user is not postgres, patch by TBP2k18 on github
+* misc: avoid flooding log files with warning about non used nodes, suggested by timdeluxe on github
 * misc: few typos fixes, YanChii
 
 

diff --git a/script/pgsqlms b/script/pgsqlms
@@ -482,7 +482,7 @@ sub _pg_isready {
     # Add 60s to the timeout or use a 24h timeout fallback to make sure
     # Pacemaker will give up before us and take decisions
     my $timeout = ( _get_action_timeout() || 60*60*24 )  + 60;
-    my $rc = _runas( $PGISREADY, '-h', $pghost, '-p', $pgport, '-t', $timeout );
+    my $rc = _runas( $PGISREADY, '-h', $pghost, '-p', $pgport, '-d', 'postgres', '-t', $timeout );
 
     # Possible error codes:
     #   1: ping rejected (usually when instance is in startup, in crash