You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to explain (for example in client-configuration.md that single connection is sufficient most of the time and therefore there is no need for connection pooling.
I was looking in docs for options regarding connection pools (as I usually do when I set up the database client) and i found none (except for isolated connection pool). As I looked briefly it seems that commands are sent to the server as fast as the underlying socket allows it
The text was updated successfully, but these errors were encountered:
Description
It would be great to explain (for example in client-configuration.md that single connection is sufficient most of the time and therefore there is no need for connection pooling.
I was looking in docs for options regarding connection pools (as I usually do when I set up the database client) and i found none (except for isolated connection pool). As I looked briefly it seems that commands are sent to the server as fast as the underlying socket allows it
The text was updated successfully, but these errors were encountered: