From 07690aab46ed5530643942726b27a503995dd835 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sat, 8 Apr 2023 10:50:46 -0400 Subject: [PATCH] Suppress bogus printout during new 035_standby_logical_decoding.pl test. Our convention for some time has been that successful tests shouldn't print anything on stderr. A stray "diag" call violated that, and for that matter messed up the normal TAP progress display. --- src/test/recovery/t/035_standby_logical_decoding.pl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/test/recovery/t/035_standby_logical_decoding.pl b/src/test/recovery/t/035_standby_logical_decoding.pl index 150290bbcd5..ba98a18bd20 100644 --- a/src/test/recovery/t/035_standby_logical_decoding.pl +++ b/src/test/recovery/t/035_standby_logical_decoding.pl @@ -460,7 +460,7 @@ $logstart = -s $node_standby->logfile; reactive_slots_change_hfs_and_wait_for_xmins('row_removal_', 'shared_row_removal_', 0, 1); # Trigger the conflict -diag $node_primary->safe_psql('testdb', qq[ +$node_primary->safe_psql('testdb', qq[ CREATE ROLE create_trash; DROP ROLE create_trash; VACUUM pg_authid; -- 2.39.5