From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Suppress bogus printout during new 035_standby_logical_decoding.
Date: Sat, 08 Apr 2023 14:50:51 +0000
Message-ID: <E1pl9ty-0023gK-Gq@gemulon.postgresql.org> (raw)
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.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/07690aab46ed5530643942726b27a503995dd835
Modified Files
--------------
src/test/recovery/t/035_standby_logical_decoding.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Suppress bogus printout during new 035_standby_logical_decoding.
In-Reply-To: <E1pl9ty-0023gK-Gq@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox