From: Álvaro Herrera <alvherre@kurilemu.de>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: pg_dump tests: don't put dumps in stdout
Date: Tue, 25 Nov 2025 18:12:48 +0000
Message-ID: <E1vNxWx-001NWP-31@gemulon.postgresql.org> (raw)
pg_dump tests: don't put dumps in stdout
This bloats the regression log files for no reason.
Backpatch to 18; no further only because it fails to apply cleanly.
(It's just whitespace change that conflicts, but I don't think this
warrants more effort than this.)
Discussion: https://postgr.es/m/202511251218.zfs4nu2qnh2m@alvherre.pgsql
Branch
------
REL_18_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/0e4b1af78d7c10baebbdcace9a37c9e304708bc1
Modified Files
--------------
src/bin/pg_dump/t/002_pg_dump.pl | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
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: alvherre@kurilemu.de, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: pg_dump tests: don't put dumps in stdout
In-Reply-To: <E1vNxWx-001NWP-31@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