Use cursor_sharing = force by default again #1745
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
it actually reverts rsim#1503 rsim#1498 implemented prepared statements for dictionary queries. However rsim#1713 restored non-prepared statements for `column_definitions` and `pk_and_sequence_for`, which likely have caused longer elapsed time for these queries reported at rsim#1720 Those who needs 'cursor_sharing = exact' can specify its own value to .database.yml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
It actually reverts #1503
#1498 implemented prepared statements for dictionary queries. However #1713 restored non-prepared statements for
column_definitionsandpk_and_sequence_for, which likely have causedlonger elapsed time for these queries reported at #1720
Those who need 'cursor_sharing = exact' can specify its own value to .database.yml