Repository navigation
Preserve exact PostgreSQL top-N ordering - #43
Merged
Merged
Conversation
Signed-off-by: Christian Weilbach <christian@weilbach.name>
Signed-off-by: Christian Weilbach <christian@weilbach.name>
Signed-off-by: Christian Weilbach <christian@weilbach.name>
Signed-off-by: Christian Weilbach <christian@weilbach.name>
Signed-off-by: Christian Weilbach <christian@weilbach.name>
Signed-off-by: Christian Weilbach <christian@weilbach.name>
Signed-off-by: Christian Weilbach <christian@weilbach.name>
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.
Summary
Motivation
The pg-datahike secondary workload exposed correctness issues at int64 boundaries and a deep-OFFSET amplification: OFFSET 50000 repeatedly sorted the same generation and took about 10.5 seconds. Requesting the exact bounded prefix once reduces that case to about 0.32 seconds. This remains O(offset); keyset continuations are separate follow-up work.
Validation