This repository was archived by the owner on May 24, 2023. It is now read-only.
Statements do not reserve connections #21
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arnehormann
added a commit
that referenced
this pull request
Nov 30, 2013
Statements do not reserve connections
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Where did you get this information from? Did you observe some kind of resource exhaustion because of statements?
Statements do not reserve any connections and AFAIK they also do not keep any connections open.
I've seen a lot of cases where people prepared statements, executed them once and immediately closed them again, although the exact same query was made frequently.
I think the changed paragraph motivates people even further to do things like this.