summaryrefslogtreecommitdiff
path: root/src/test
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2023-04-08 10:50:46 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2023-04-08 10:50:46 -0400
commit07690aab46ed5530643942726b27a503995dd835 (patch)
tree411246321d2cafa207bf6412c8ecb3570a0acdfd /src/test
parent2e57ffe12f6b5c1498f29cb7c0d9e17c797d9da6 (diff)
downloadpostgresql-07690aab46ed5530643942726b27a503995dd835.tar.gz
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.
Diffstat (limited to 'src/test')
-rw-r--r--src/test/recovery/t/035_standby_logical_decoding.pl2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/test/recovery/t/035_standby_logical_decoding.pl b/src/test/recovery/t/035_standby_logical_decoding.pl
index 150290bbcd..ba98a18bd2 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;