Test: unbreak 039.log_backend_messages.

Commit 8ff2b9f6e mistakenly put synchronous commit parameters in
pgpool.conf.  Unbreak the test by putting the parameters in
postgresql.conf. Also check if clustering mode is streaming
replication. Because that parameters causes suspends PostgreSQL if
clustering mode is other than streaming replication.

Backpatch-through: v4.6

diff --git a/src/test/regression/tests/039.log_backend_messages/test.sh b/src/test/regression/tests/039.log_backend_messages/test.sh
index 23e077ebb681d5334be319f75cc2653175327fae..6fe672e46f3e8caf0c374d3e627e159a90ea613b 100755 (executable)
--- a/src/test/regression/tests/039.log_backend_messages/test.sh
+++ b/src/test/regression/tests/039.log_backend_messages/test.sh
@@ -29,15 +29,19 @@ do
     # We set connection_cache to off so that each time client connects
     # to pgpool, it receives ready for query from backend.
     # We set synchronous_commit = remote_apply, and synchronous_standby_names = 'server1'
-    # so that updation to primary is replicated to standby with no lag.
+    # in streaming replication mode so that updation to primary is replicated to standby with no lag.
         cat >> etc/pgpool.conf <<EOF
 backend_weight0 = 0
 client_min_messages = log
 log_per_node_statement = off
 connection_cache = off
+EOF
+       if [ $mode = "s" ];then
+            cat >> data0/postgresql.conf <<EOF
 synchronous_commit = remote_apply
 synchronous_standby_names = 'server1'
 EOF
+       fi
     for option in none terse verbose
     do
        echo "==== mode: $mode option: $option ===" >> result