[WIP] opt: add hint to ignore preserved-multiplicity consistency #82188
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
|
This change is |
michae2
force-pushed
the
ignore_preserved_consistency
branch
2 times, most recently
from
733de8e to
6e3908c
Compare
For some queries (e.g. SELECT FOR UPDATE SKIP LOCKED) we need to disable optimizations that depend on preserved-multiplicity consistency of tables. Add an IGNORE_PRESERVED_CONSISTENCY hint that turns off these optimizations. With this hint, we will no longer use optimizations that assume: - a PK row exists for every secondary index row - a FK row exists for every referenced FK Release note: None
michae2
force-pushed
the
ignore_preserved_consistency
branch
from
6e3908c to
4b350da
Compare
michae2
changed the title
|
Note to self: this is a little bit broken. Some of the rules that I modified would work fine and probably don't need to be modified. Also this needs tests. |
|
Tracking issue is: #83156 |
|
Notes from talking to @rytaft:
|
craig bot
pushed a commit
that referenced
this pull request
Aug 10, 2022
85720: sql: parser and optimizer support FOR {UPDATE,SHARE} SKIP LOCKED r=rytaft a=rytaft
This PR adds support for `SKIP LOCKED` by building on commits from #83627 and #82188. See below for details.
**sql: enable the skip-locked wait policy**
Now that KV support this, we can pass the wait policy through.
Fixes #40476
Release note (sql change): `SELECT ... FOR {UPDATE,SHARE} SKIP LOCKED`
is now supported. The option can be used to skip rows that cannot be
immediately locked instead of blocking on contended row-level lock
acquisition.
**opt: optimizer updates for support of SKIP LOCKED**
For queries using `SELECT FOR {SHARE,UPDATE} SKIP LOCKED`, we need to disable
optimizations that depend on preserved-multiplicity consistency of
tables. When `SKIP LOCKED` is used, we will no longer use optimizations that
assume:
- a PK row exists for every secondary index row
- a PK row exists for every referencing FK (if the PK table uses `SKIP LOCKED`)
One result of this change is that we will no longer push limits into index
joins if the primary index uses locking wait policy `SKIP LOCKED`.
This commit also disallows use of multiple column families in tables scanned
with `SKIP LOCKED`, since it could result in returning partial rows.
Release note: None
Co-authored-by: Michael Erickson <[email protected]>
Co-authored-by: Nathan VanBenschoten <[email protected]>
Co-authored-by: Rebecca Taft <[email protected]>
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.
For some queries (e.g. SELECT FOR UPDATE SKIP LOCKED) we need to disable
optimizations that depend on preserved-multiplicity consistency of
tables. Add an IGNORE_PRESERVED_CONSISTENCY hint that turns off these
optimizations. With this hint, we will no longer use optimizations that
assume:
Release note: None