pgsql: use subquery to plan GetNotification query #182
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
This change enables the query planner to wait and sort the result set of our query rather than attempting to re-use the layer table's index for the ORDER BY clause. Because the result set is always small, this makes queries that were previous tens of seconds, now tens of milliseconds.
jzelinskie
added
area/performance
|
LGTM |
jzelinskie
added a commit
that referenced
this pull request
May 20, 2016
This change enables the query planner to wait and sort the result set of our query rather than attempting to re-use the layer table's index for the ORDER BY clause. Because the result set is always small, this makes queries that were previous tens of seconds, now tens of milliseconds.
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.
This change enables the query planner to wait and sort the result set of
our query rather than attempting to re-use the layer table's index for
the ORDER BY clause. Because the result set is always small, this makes
queries that were previous tens of seconds, now tens of milliseconds.