Upgrade to Go 1.19 (#2347)

testing/dbtest/docs.go

@@ -6,20 +6,20 @@
 // To use this package in a test add something like the following in the
 // beginning of the test:
 //
-//  c, u, _, err := dbtest.StartUsingTemplate(dbtest.Postgres)
-//  require.NoError(t, err)
-//  t.Cleanup(func() {
-//    require.NoError(t, c())
-//  })
-//  // use u to get a connection to the new database
-//  dBase, err := common.SqlOpen("postgres", u)
+//	c, u, _, err := dbtest.StartUsingTemplate(dbtest.Postgres)
+//	require.NoError(t, err)
+//	t.Cleanup(func() {
+//	  require.NoError(t, c())
+//	})
+//	// use u to get a connection to the new database
+//	dBase, err := common.SqlOpen("postgres", u)
 //
 // By default this uses a template that already has all of the boundary
 // migrations run. If a test needs a database without any migrations, like in
 // the case where the migration code needs to be tested, a different template
 // can be specified. This should generally be template1:
 //
-//  c, u, _, err := dbtest.StartUsingTemplate(dbtest.Postgres, dbtest.WithTemplate(dbtest.Template1))
+//	c, u, _, err := dbtest.StartUsingTemplate(dbtest.Postgres, dbtest.WithTemplate(dbtest.Template1))
 //
 // See https://www.postgresql.org/docs/13/manage-ag-templatedbs.html
 package dbtest

testing/dbtest/session_list_benchmarks_dump_generation_test.go

@@ -33,9 +33,10 @@ import (
 // to predictable files for use in benchmarking.
 //
 // Each database dump contains:
-// * N number of sessions, with each session having M connections.
-// * P users, each owning an even amount of the sessions. All users
-//   use the password "testpassword" to login.
+//   - N number of sessions, with each session having M connections.
+//   - P users, each owning an even amount of the sessions. All users
+//     use the password "testpassword" to login.
+//
 // It is safe for users of these dumps to assume all of this, for the variables
 // N, M and P defined in the "scenarios" struct below.
 func TestGenerateSessionBenchmarkTemplateDumps(t *testing.T) {