Read hypertable max time value with an ordered scan - #10379
Open
svenklemm wants to merge 1 commit into
Open
Conversation
|
@akuzm, @antekresic: please review this pull request.
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
The max value of a hypertable's open dimension was read with a max() aggregate. For UUID time columns the aggregate argument is an expression that extracts the timestamp from the UUID. Because the argument is an expression and not a plain column, the planner cannot rewrite the aggregate into a min/max aggregate, so it reads every row instead. Also lock down search_path for the SPI execution and fix a sql injection vulnerability in the UUID path.
svenklemm
force-pushed
the
sven/cagg_max
branch
from
August 2, 2026 15:57
1c6895b to
4c5077b
Compare
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
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.
The max value of a hypertable's open dimension was read with a max()
aggregate. For UUID time columns the aggregate argument is an expression
that extracts the timestamp from the UUID. Because the argument is an
expression and not a plain column, the planner cannot rewrite the
aggregate into a min/max aggregate, so it reads every row instead.
Also lock down search_path for the SPI execution and fix a sql
injection vulnerability in the UUID path.