database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-14 18:42:34 +03:00
Code Activity

Fix test name and username used in failed connection attempts

Browse Source 
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
This commit is contained in:
Heikki Linnakangas
2025-03-09 19:47:55 +02:00
parent fedfcf6650
commit 2a943afcff
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/test/postmaster/t/002_connection_limits.pl
View File

@ -80,7 +80,7 @@ push(@sessions, background_psql_as_user('regress_regular'));
connect_fails_wait(
$node,
"dbname=postgres user=regress_regular",
"reserved_connections limit",
"regular connections limit",
expected_stderr =>
qr/FATAL: remaining connection slots are reserved for roles with privileges of the "pg_use_reserved_connections" role/
);
@ -89,7 +89,7 @@ push(@sessions, background_psql_as_user('regress_reserved'));
push(@sessions, background_psql_as_user('regress_reserved'));
connect_fails_wait(
$node,
"dbname=postgres user=regress_regular",
"dbname=postgres user=regress_reserved",
"reserved_connections limit",
expected_stderr =>
qr/FATAL: remaining connection slots are reserved for roles with the SUPERUSER attribute/