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.
Thanks to a report from @jamessewell we dug into some aggregate performance issues.
This hints that memory context swap calls like these should always be inline, and should improve performance in many cases.
Using an example of
Before:
After:
pgx_tests=# SELECT RustMaxInternal(value) FROM generate_series(0, 400000) as value; rustmaxinternal ----------------- 400000 (1 row) Time: 128.002 ms
A single run isn't really meaningful, but we think this hinting may yield some perf improvements where the optimizer does actually need hinting. Further, it does make sense to inline these calls, since they always happen, have small bodies, and it's performance sensitive bits of the code.