我有一個(gè)請(qǐng)求者，負(fù)責(zé)管理針對(duì) Azure SQL 數(shù)據(jù)庫(kù)的 SQL 查詢。負(fù)責(zé)事務(wù)查詢的函數(shù)如下：import (    "context"    "database/sql"    "fmt"    "log"    "strings"    "time"    "github.com/cenkalti/backoff"    _ "github.com/denisenkom/go-mssqldb" // Need to import the SQL driver so we can tell Golang how to interpret our requests)// Helper function that does a single Exec with a transaction with a context on a query and variables.// This function will return an error if there are any failuresfunc (requester *Requester) doTransaction(ctx context.Context,     isolation sql.IsolationLevel, txFunc func(*sql.Tx) error) error {    // First, get the database connection; if this fails then return an error    conn, err := requester.getConn(ctx)    if err != nil {        return err    }    // Before we continue on, ensure that the connection is clsoed and returned to the connection pool    defer func() {        if err := conn.Close(); err != nil {            log.Printf("Close failed, error: %v", err)        }    }()    // Next, start the transaction with the given context and the default isolation    tx, err := requester.getTx(ctx, conn, isolation)    if err != nil {        return err    }總的來說，這很有效。我注意到的一個(gè)問題是，當(dāng)各個(gè)請(qǐng)求之間經(jīng)過很長(zhǎng)時(shí)間時(shí)，我會(huì)在第一次重試時(shí)遇到錯(cuò)誤，然后在后續(xù)重試時(shí)出錯(cuò)，最終導(dǎo)致失敗。我的想法是，問題與此錯(cuò)誤有關(guān)。從本質(zhì)上講，微軟似乎在30分鐘后使空閑請(qǐng)求無效。但是，由于我將最大空閑時(shí)間設(shè)置為10分鐘，因此這應(yīng)該不是問題所在。i/o timeoutbad connection這是怎么回事，我該如何解決這個(gè)問題？