Optimization - Reusing Antlr4ResultHandler Initialization #1107
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
|
@Munmud can you make this pull request for each of the previous PG versions? For PG 11,12,13, and 14? Thanks |
|
Sure. Working on it. Thanks |
This was referenced Aug 19, 2023
jrgemignani
pushed a commit
that referenced
this pull request
Dec 13, 2023
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.
Description
As mentioned in issue #1106,
This pull request aims to optimize the current implementation of the
Antlr4ResultHandlerinitialization process, resulting in improved query processing time and reduced overhead. Currently, for each query made, theAntlr4ResultHandleris repeatedly initialized, leading to unnecessary performance bottlenecks. To address this issue, we propose initializing the handler only once and then reusing it for subsequent queries.