[Go] [Postgres] Is DBTX interface concurrent-safe?

[vrv7567]

From the sqlc docs,

queries := tutorial.New(conn)  // New queries struct containing DBTX interface

// list all authors
authors, err := queries.ListAuthors(ctx)
// yada-yada

// create an author
insertedAuthor, err := queries.CreateAuthor(ctx, tutorial.CreateAuthorParams{
                                     Name: "Brian Kernighan",
                                     Bio:  pgtype.Text{String: "Co-author of The C Programming Language and The Go Programming Language", Valid: true},
})
// yada-yada

// get the author we just inserted
fetchedAuthor, err := queries.GetAuthor(ctx, insertedAuthor.ID)
// yada-yada

The queries struct is initialized once and used for all subsequent db operations. It makes sense since we are calling them sequentially.

However I have use-case where concurrent db-operations might happen. In this case, should queries struct be initialized each-time the db-operation is called

func ListAuthors(conn *pgxpool.Pool) {
   queries := tutorial.New(conn)
   authors, err := queries.ListAuthors(ctx)
}

func InsertAuthor(conn *pgxpool.Pool) {
   queries := tutorial.New(conn)
   authors, err := queries.CreateAuthor(ctx)
}

OR

Can I pass reference of queries struct and use it concurrently in my db-operations

func ListAuthors(q *Queries) {
   authors, err := q.ListAuthors(ctx)
}

func InsertAuthor(q *Queries) {
   authors, err := q.CreateAuthor(ctx)
}

[vrv7567]

I decided to go with 1st approach as you can't really use transactions with 2nd approach. The queries struct has DBTX interface unexported