Run dispatch queries with preparedStatements #1410
Merged
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
Our experiments showed that running this query as a prepared statement causes postgres to be more consistent on choosing a query plan to run based on the size of the underlying indexes. No change in functionality is added by this change.
ramonfigueiredo
approved these changes
Jul 13, 2024
Signed-off-by: Diego Tavares <dtavares@imageworks.com>
DiegoTavares
merged commit d7f5259
into
AcademySoftwareFoundation:master
12 checks passed
|
@bcipriano FYI |
n-jay
pushed a commit
to n-jay/OpenCue
that referenced
this pull request
Jul 26, 2024
…on#1410) Our experiments showed that running this query as a prepared statement causes postgres to be more consistent on choosing a query plan to run based on the size of the underlying indexes. No change in functionality is added by this change. Signed-off-by: Diego Tavares <dtavares@imageworks.com>
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.
Our experiments showed that running this query as a prepared statement makes Postgres more consistent in choosing a query plan to run based on the size of the underlying indexes.
No change in functionality is added by this change.