release-22.1: opt: add support for NULLS LAST with DISTINCT ON #93608
Conversation
This file contains 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
![blathers-crl[bot]](https://avatars.githubusercontent.com/in/59700?s=60&v=4){kind=small}
blathers-crl
bot
force-pushed
the
blathers/backport-release-22.1-93567
branch
from
34fbc2f to
62dac05
Compare
|
Thanks for opening a backport. Please check the backport criteria before merging:
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
Add a brief release justification to the body of your PR to justify this backport. Some other things to consider:
|
blathers-crl
bot
added
blathers-backport
|
This change is |
|
Let's hold off on merging this backport until #93719 is fixed. |
msirek
approved these changes
Dec 15, 2022
There was a problem hiding this comment.
Reviewed 3 of 3 files at r1, all commit messages.
Reviewable status:complete! 1 of 0 LGTMs obtained (waiting on @michae2 and @rytaft)
rytaft
force-pushed
the
blathers/backport-release-22.1-93567
branch
from
fb5d660 to
50a7cb1
Compare
This commit adds an exception for the requirement that the ORDER BY clause of a DISTINCT ON query must contain only columns in the ON clause. Specifically, it allows expressions of the form `col IS NULL`, where col is one of the ON columns. This is needed to support NULLS LAST, since we implement NULLS LAST by synthesizing a `col IS NULL` ordering column. The approach feels a bit hacky, but it seems like the smallest, lowest risk option available. Fixes #90763 Release note (bug fix): Fixed an issue where DISTINCT ON queries would fail with the error "SELECT DISTINCT ON expressions must match initial ORDER BY expressions" when the query included an ORDER BY clause containing ASC NULLS LAST or DESC NULLS FIRST.
rytaft
force-pushed
the
blathers/backport-release-22.1-93567
branch
from
50a7cb1 to
ce7c5c0
Compare
msirek
approved these changes
Dec 15, 2022
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.
Backport 1/1 commits from #93567 on behalf of @rytaft.
/cc @cockroachdb/release
This commit adds an exception for the requirement that the
ORDER BYclause of aDISTINCT ONquery must contain only columns in theONclause. Specifically, it allows expressions of the formcol IS NULL, wherecolis one of theONcolumns. This is needed to supportNULLS LAST, since we implementNULLS LASTby synthesizing acol IS NULLordering column.The approach feels a bit hacky, but it seems like the smallest, lowest risk option available.
Fixes #90763
Release note (bug fix): Fixed an issue where
DISTINCT ONqueries would fail with the error "SELECT DISTINCT ON expressions must match initial ORDER BY expressions" when the query included anORDER BYclause containingASC NULLS LASTorDESC NULLS FIRST.Release justification: Low-risk bug fix.