Why would I not want to set interpolateParams=true?

I'm sorry for the newbie question.

From what I've read it seems that each database/sql Query / Exec with args that I issue is prepared, executed, and closed on the server, resulting in 3 round-trips. And I can avoid that behavior by setting interpolateParams=true. Are there any downsides to setting interpolateParams to true? If I don't set it and a prepared statement is created behind the scenes as a result of issuing a Query / Exec, and later another Query / Exec with the same text is issued, does the driver remember the earlier-prepared statement? As far as I can tell it doesn't, and another Prepare call is made to the server, so it seems that the prepared statement that is created behind the scenes as a result of issuing a Query / Exec is single-use only, which seems wasteful.

Also, I'm thinking that if I've set interpolateParams=true and I want to create and re-use a prepared statement, I can still call Prepare in my code to create the prepared statement.

Am I looking at this correctly?

[methane]

You're right. interpolateParams=true doesn't affect to explicit DB.Prepare and Stmt.Exec.
If you meets some trouble relating to interpolateParams, you can avoid it by using explicit prepared statement.
So there is no downside when you know what "interpolateParams" means.

Thank you for the quick answer!

[elvisxiong2023]

go: trpc.group/trpc-go/trpc-database/gorm@v1.0.0: verifying go.mod: trpc.group/trpc-go/trpc-database/gorm@v1.0.0/go.mod: initializing sumdb.Client: checking tree#2910060: Get "https://sum.woa.com/tile/8/2/000.p/44": dial tcp 175.27.22.2:443: i/o timeout