From 8ff2b9f6e7e341b4160bd3b51db464c471c3a97f Mon Sep 17 00:00:00 2001 From: Tatsuo Ishii Date: Sun, 31 Aug 2025 15:17:54 +0900 Subject: [PATCH] Test: stabilize 039.log_backend_messages test. In the test a query is sent to standby server right after rows are inserted into primary server. Due to a replication lag, the inserted rows could not be found on the standby in slower machines. This commit tries to fix the issue by using synchronous replication with remote_apply option. Backpatch-through: v4.2 --- src/test/regression/tests/039.log_backend_messages/test.sh | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) 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 d89ba5494..23e077ebb 100755 --- a/src/test/regression/tests/039.log_backend_messages/test.sh +++ b/src/test/regression/tests/039.log_backend_messages/test.sh @@ -23,16 +23,20 @@ do echo > result - # We set backend_weight0 to 0 to send ready queries to backend 1. + # We set backend_weight0 to send read queries to backend 1. # We set client_min_messages to log so that log messages appear on # the client screen. # 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. cat >> etc/pgpool.conf <