Scope

• Do not include the "connections in use by cursors: x, connections in use by transactions: y, connections in use by other operations: z" part of the WaitQueueTimeoutError when connections are not being pinned.

Background & Motivation

When connected to a Load Balancers, drivers are required to pin connections to cursors and transactions.
Drivers are required to report the pinned connections in the WaitQueueTimeoutError.

The Go driver always reports pinned connections in WaitQueueTimeoutError, even if no connection pinning occurs.

That can cause confusing error messages when not connected to a load balanced cluster. Example:

timed out while checking out a connection from connection pool: context canceled; maxPoolSize: 300, connections in use by cursors: 0, connections in use by transactions: 0, connections in use by other operations: 0