My suggestion is the documentation makes clear that some drivers will cancel the execution of the query whilst others will only cancel waiting for the query results but the execution will still complete behind the scenes.

This is a very important distinction.

See: go-sql-driver/mysql#863 for more details.
@methane is one of the key contributors to the popular mysql driver.

I found out this issue is more serious than a mere "documentation issue" forewarning the pitfalls.

See: go-sql-driver/mysql#863 (comment)

I have created an "empty" proposal: #28074 for auditing purposes.

I'll look into more detail in the documentation.

My suggestion is the documentation makes clear that some drivers will cancel the execution of the query whilst others will only cancel waiting for the query results but the execution will still complete behind the scenes.

This is a very important distinction.

Why is it very important?

Even though driver support cancelling query on the server, it only saves some CPU usage.

Canceling remote query is hard and nondeterministic problem. You shouldn't rely on behaviour of canceling.
In case of go-sql-driver/mysql#863, you should use transaction.

There is already really clear documentation. At the top of the page of https://golang.org/pkg/database/sql/

Drivers that do not support context cancelation will not return until after the query is completed.

I think that is clear enough. Closing.

Some drivers such as MySQL driver do support cancellation.

I was trying to make clear that even if the driver does support cancellation, the documentation should warn that successfully cancelling from Go's point of view does not imply that the query is cancelled from databases point of view.

In the case of MySQL, cancelling does not mean that MySQL has cancelled the execution of the query.