[#20393] YSQL: Stabilize testAlterRoleConfiguration with Connection M…

…anager enabled

Summary:
The test `org.yb.pgsql.TestPgAuthorization.testAlterRoleConfiguration` fails with Connection Manager enabled as the test requires unique physical connections in order to view the changes made via the ALTER ROLE SET query being fired in this test. There are other JUnit tests that already make use of this functionality which pass with Connection Manager enabled; this patch skips the test when Connection Manager is enabled.

This situation may be tracked via stickiness of connections later on: DB-11187

Jira: DB-9382

Test Plan:
Jenkins: enable connection manager, test regex: .*TestPgAuthorization.*

./yb_build.sh --enable-ysql-conn-mgr-test --java-test org.yb.pgsql.TestPgAuthorization#testAlterRoleConfiguration

Reviewers: nkumar, mkumar

Reviewed By: nkumar

Differential Revision: https://phorge.dev.yugabyte.com/D34617

java/yb-pgsql/src/test/java/org/yb/pgsql/TestPgAuthorization.java

@@ -14,6 +14,7 @@
 package org.yb.pgsql;
 
 import static org.yb.AssertionWrappers.*;
+import static org.junit.Assume.*;
 
 import org.hamcrest.CoreMatchers;
 import org.junit.Test;
@@ -1078,6 +1079,13 @@ public void testDefaultRoles() throws Exception {
 
   @Test
   public void testAlterRoleConfiguration() throws Exception {
+
+    // The test fails with Connection Manager as it is expected that a new
+    // session would latch onto a new physical connection. Instead, two logical
+    // connections use the same physical connection, leading to unexpected
+    // results as per the expectations of the test.
+    assumeFalse(BasePgSQLTest.UNIQUE_PHYSICAL_CONNS_NEEDED, isTestRunningWithConnectionManager());
+
     try (Statement statement = connection.createStatement()) {
       statement.execute("CREATE ROLE test_role LOGIN");