Skip to content

Backport to 2.27.x: #9955: Forbid Batch Sorted Merge on multikey minmax index - #9959

Closed
timescale-automation wants to merge 7 commits into
2.27.xfrom
backport/2.27.x/9955
Closed

Backport to 2.27.x: #9955: Forbid Batch Sorted Merge on multikey minmax index#9959
timescale-automation wants to merge 7 commits into
2.27.xfrom
backport/2.27.x/9955

Conversation

@timescale-automation

Copy link
Copy Markdown
Member

This is an automated backport of #9955: Forbid Batch Sorted Merge on multikey minmax index.
The original issue is #9922.
This PR will be merged automatically after all the relevant CI checks pass. If this fix should not be backported, or will be backported manually, just close this PR. You can use the backport branch to add your changes, it won't be modified automatically anymore.

For more details, please see the documentation

Original description

Forbid Batch Sorted Merge on multikey minmax index

Fixes #9922

Forbids Batch Sorted Merge when there is no firstlast index on a non-leading order by column.

Fixes #9922

Forbids Batch Sorted Merge when there is no firstlast index on a
non-leading order by column.

(cherry picked from commit 763e7b1)
@philkra

philkra commented Jun 16, 2026

Copy link
Copy Markdown
Member

Closing as this will not get merged, new version branch 2.28.x

@philkra philkra closed this Jun 16, 2026
auto-merge was automatically disabled June 16, 2026 15:23

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

is-auto-backport PR created by backport automation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants