sql: TestRandomSyntaxFunctions use resettable timeouts

Previously, TestRandomSyntaxFunctions could flake since
some operations could take a long time. A resettable timeout
makes things more dynamic, and allows timeouts to be extended
while other connections make progress for a limited time, which
can help with certain builtins that are schema changes (i.e. they
will wait on other connections).

Fixes: cockroachdb#99182

Release note: None

Author: fqazi

pkg/sql/tests/rsg_test.go

@@ -352,7 +352,8 @@ func TestRandomSyntaxFunctions(t *testing.T) {
 					continue
 				case "crdb_internal.reset_sql_stats",
 					"crdb_internal.check_consistency",
-					"crdb_internal.request_statement_bundle":
+					"crdb_internal.request_statement_bundle",
+					"crdb_internal.reset_activity_tables":
 					// Skipped due to long execution time.
 					continue
 				}
@@ -414,7 +415,11 @@ func TestRandomSyntaxFunctions(t *testing.T) {
 			limit = " LIMIT 100"
 		}
 		s := fmt.Sprintf("SELECT %s(%s) %s", nb.name, strings.Join(args, ", "), limit)
-		return db.exec(t, ctx, s)
+		// Use a re-settable timeout since in concurrent scenario some operations may
+		// involve schema changes like truncates. In general this should make
+		// this test more resilient as the timeouts are reset as long progress
+		// is made on *some* connection.
+		return db.execWithResettableTimeout(t, ctx, s, *flagRSGExecTimeout, *flagRSGGoRoutines)
 	})
 }