chore(deps): bump @query-doctor/core to 0.25.0 - #227
Merged
Conversation
0.25.0 adds `maxSerializedBytes` and `maxStoredBytes` to the statistics export. The analyzer already calls `Statistics.dumpStats`, so this range bump is what makes runs collect them. A payload then reports a range instead of one number from a mean, and a candidate index on a column too wide for a btree key is dropped. A 0.x caret does not cross a minor, so ^0.24.0 would never have taken it.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
More details via MCP → get_ci_run({ runId: "019ff691-a99f-718d-9ce2-2a1027d4252f" }) · view run · docs
3 queries read against main on assumed statistics of 10,000,000 rows per table. Sync production stats for costs measured against your real data.
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
1 participant
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.
Goal
Make CI runs collect the per-column extremes that
@query-doctor/core@0.25.0added. Nothing collects them today, so a payload is still a point estimate from a mean and an index candidate is never checked for width.Site side: Query-Doctor/Site#3955 is the feature, #3961 published core.
What
Before, a statistics dump carried a column's average serialized size. After, it also carries the widest value the sample saw, serialized and as stored.
Two things use them. A payload becomes a range: on this repo's own history query the mean gives 448 KB and the same column's maximum gives 42.5 MB. And a candidate index on a column over 2,704 stored bytes is dropped, because Postgres refuses that key —
index row requires 1152048 bytes, maximum size is 8191on a real row ofci_runs_queries.optimization.No analyzer code changes.
Statistics.dumpStatsalready does the sampling; the range bump is what lets a run see the version that measures both extremes.How
"@query-doctor/core": "^0.24.0"becomes"^0.25.0", with the lockfile. A0.xcaret does not cross a minor.Tests
No new test, since no analyzer code changed. Existing suite passes: 440 tests across 43 files. Typecheck and build clean.