doc: avoid perf degradation because of jit #32
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
EQuincerot
commented
Dec 12, 2025
EQuincerot
commented
Dec 12, 2025
EQuincerot
commented
Dec 12, 2025
AliceLoeser
approved these changes
Dec 16, 2025
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.
As pg_no_seqscan extension needs
enable_seqscan = offthe average cost of queries increases strongly.When working on partition tables with many partition or when join many tables, the cost was big enough to let PG enable jit which is rarely a good choice in terms of performance for local/test/ci database.
jit_above_costwas already set very high, but it's not enough for some specific use cases.Here we increase the recommendation.