fix: handle 'connection reset by peer' in postgres test utility

blink-so[bot] · ibetitsmike · blink-so[bot] · commit 2bc981c8102b · 2025-06-18T08:23:06.000Z
Add 'connection reset by peer' to the list of errors that should trigger starting a new postgres container in the test utility. This fixes flaky tests that fail when PostgreSQL resets connections. Fixes: coder/internal#695 Co-authored-by: ibetitsmike <203725896+ibetitsmike@users.noreply.github.com>
diff --git a/coderd/database/dbtestutil/postgres.go b/coderd/database/dbtestutil/postgres.go
@@ -71,6 +71,7 @@ func initDefaultConnection(t TBSubset) error {
 		errSubstrings := []string{
 			"connection refused",          // this happens on Linux when there's nothing listening on the port
 			"No connection could be made", // like above but Windows
+			"connection reset by peer",    // this happens when PostgreSQL resets the connection
 		}
 		errString := dbErr.Error()
 		for _, errSubstring := range errSubstrings {

Original file line number	Diff line number	Diff line change
`@@ -71,6 +71,7 @@ func initDefaultConnection(t TBSubset) error {`
`71`	`71`	`errSubstrings := []string{`
`72`	`72`	`"connection refused", // this happens on Linux when there's nothing listening on the port`
`73`	`73`	`"No connection could be made", // like above but Windows`
	`74`	`+ "connection reset by peer", // this happens when PostgreSQL resets the connection`
`74`	`75`	`}`
`75`	`76`	`errString := dbErr.Error()`
`76`	`77`	`for _, errSubstring := range errSubstrings {`