Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 2a943af

Browse files
committed
Fix test name and username used in failed connection attempts
The first failed connection tests the "regular" connections limit, not the reserved limit. In the second failed connection, the username doesn't really matter, but since the previous successful connections used "regress_reserved", it seems weird to switch back to "regress_regular" for the expected-to-fail attempt. Discussion: https://www.postgresql.org/message-id/fd5e9523-78d3-4270-86b2-fd1b1eeb4fc9@iki.fi
1 parent fedfcf6 commit 2a943af

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/test/postmaster/t/002_connection_limits.pl

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ sub connect_fails_wait
8080
connect_fails_wait(
8181
$node,
8282
"dbname=postgres user=regress_regular",
83-
"reserved_connections limit",
83+
"regular connections limit",
8484
expected_stderr =>
8585
qr/FATAL: remaining connection slots are reserved for roles with privileges of the "pg_use_reserved_connections" role/
8686
);
@@ -89,7 +89,7 @@ sub connect_fails_wait
8989
push(@sessions, background_psql_as_user('regress_reserved'));
9090
connect_fails_wait(
9191
$node,
92-
"dbname=postgres user=regress_regular",
92+
"dbname=postgres user=regress_reserved",
9393
"reserved_connections limit",
9494
expected_stderr =>
9595
qr/FATAL: remaining connection slots are reserved for roles with the SUPERUSER attribute/

0 commit comments

Comments
 (0)