Skip to content

Commit b9164ea

Browse files
committed
pg_amcheck: Keep trying to fix the tests.
Commit 2418927 managed to remove one of the two places where we were checking for a "no such user" error while leaving the other one right next to it. So remove that too. In fact, remove the entire test, because the whole point of this test was to see which message we got on a failure.
1 parent 2418927 commit b9164ea

File tree

1 file changed

+1
-10
lines changed

1 file changed

+1
-10
lines changed

src/bin/pg_amcheck/t/002_nonesuch.pl

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33

44
use PostgresNode;
55
use TestLib;
6-
use Test::More tests => 75;
6+
use Test::More tests => 72;
77

88
# Test set-up
99
my ($node, $port);
@@ -71,15 +71,6 @@
7171
[ ],
7272
'checking with a non-existent user');
7373

74-
# Failing to connect to the initial database due to bad username is an still an
75-
# error under --no-strict-names.
76-
$node->command_checks_all(
77-
[ 'pg_amcheck', '--no-strict-names', '-U', 'no_such_user', 'postgres' ],
78-
1,
79-
[ qr/^$/ ],
80-
[ qr/role "no_such_user" does not exist/ ],
81-
'checking with a non-existent user under --no-strict-names');
82-
8374
#########################################
8475
# Test checking databases without amcheck installed
8576

0 commit comments

Comments
 (0)