feat(statement_timeout): Support for PostgreSQL statement_timeout #8254
Conversation
This file contains 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
jkennedy1980
changed the title
added 6 commits
September 5, 2017 11:40
sushantdhiman
added
dependency
|
Added this option to whitelist here https://github.com/sequelize/sequelize/pull/8342/files Any pg@7.3 users can now use it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I just contributed
statement_timeoutsupport tonode-pgin version7.3.0. This PR bringsstatement_timeoutsupport to Sequelize.Statement timeout allows you to set a maximum milliseconds for all queries executed on a connection. This is useful when running on Heroku because they enforce a maximum HTTP timeout of 30 seconds. If you have long running queries, postgres continues to execute them even though the HTTP connection is closed and no one will receive the response.