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
pull/255/head
Álvaro Herrera 3 weeks ago
parent 417ac9c1ee
commit 33bb3dc2d8
No known key found for this signature in database
GPG Key ID: 1C20ACB9D5C564AE
  1. 10
      src/bin/pg_dump/t/002_pg_dump.pl

@ -5019,7 +5019,12 @@ $node->command_fails_like(
# Test dumping pg_catalog (for research -- cannot be reloaded)
$node->command_ok(
[ 'pg_dump', '--port' => $port, '--schema' => 'pg_catalog' ],
[
'pg_dump',
'--port' => $port,
'--schema' => 'pg_catalog',
'--file' => "$tempdir/pgdump_pgcatalog.dmp"
],
'pg_dump: option -n pg_catalog');
#########################################
@ -5029,7 +5034,8 @@ $node->command_ok(
[
'pg_dumpall',
'--port' => $port,
'--exclude-database' => '"myhost.mydb"'
'--exclude-database' => '"myhost.mydb"',
'--file' => "$tempdir/pgdumpall.dmp"
],
'pg_dumpall: option --exclude-database handles database names with embedded dots'
);

Loading…
Cancel
Save