From 2a943afcff444bade64ad5209f8b248d8d449383 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Sun, 9 Mar 2025 19:47:55 +0200 Subject: [PATCH] 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 --- src/test/postmaster/t/002_connection_limits.pl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/test/postmaster/t/002_connection_limits.pl b/src/test/postmaster/t/002_connection_limits.pl index 2c185eef6eb..fd670f3a8f5 100644 --- a/src/test/postmaster/t/002_connection_limits.pl +++ b/src/test/postmaster/t/002_connection_limits.pl @@ -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/ -- 2.39.5