[PGPRO-17316] Fixed a bug that appeared in e36d1644.#170
Merged
arseny114 merged 1 commit intopostgrespro:masterfrom Mar 13, 2026
Merged
[PGPRO-17316] Fixed a bug that appeared in e36d1644.#170arseny114 merged 1 commit intopostgrespro:masterfrom
arseny114 merged 1 commit intopostgrespro:masterfrom
Conversation
A bug appeared in commit e36d164, due to which, regardless of the strategy and type of the ORDER BY column, the NoMovementScanDirection direction was selected and the index followed the path with internal sorting. The bug has been fixed in this commit. Now, if possible, RUM gets the items from the scan immediately in the correct order. Tags: rum
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.
A bug appeared in commit e36d164, due to which, regardless of the strategy and type of the ORDER BY column, the NoMovementScanDirection direction was selected and the index followed the path with internal sorting.
The bug has been fixed in this commit. Now, if possible, RUM gets the items from the scan immediately in the correct order.
Tags: rum