Repository navigation
Postgres: support WHERE index_predicate in the ON CONFLICT target #2627
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
LucaCappelletti94
merged 4 commits into
apache:main
from
zvonimir-dd:postgres-on-conflict-target-predicate
Oct 24, 2026
+171
−10
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
1166605
Postgres: support WHERE index_predicate in the ON CONFLICT target
zvonimir-dd a6e54d7
Test the ON CONFLICT target predicate's span and its parse errors
zvonimir-dd 7e23b46
Make the target predicate part of ConflictTarget::Columns
zvonimir-dd a3722e6
Say SQLite accepts the ON CONFLICT target predicate too
zvonimir-dd File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| INSERT INTO t (a, b) VALUES (1, 2) ON CONFLICT (a) WHERE b > 0 DO NOTHING; | ||
| INSERT INTO t (a, b, c) VALUES (2, 2, 3) ON CONFLICT (a, c) WHERE b > 0 AND c IS NOT NULL DO UPDATE SET b = EXCLUDED.b WHERE t.b < 10; |
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should say SQLite accepts this predicate too. Its upsert grammar has the same
( indexed-column, ... ) WHERE exprtarget, and the parser reads it in every dialect. SQLite 3.51.1 runsINSERT INTO t VALUES (1, 2, 3) ON CONFLICT (a) WHERE b > 0 DO NOTHINGand rejectsON CONFLICT WHERE b > 0. With the doc naming only PostgreSQL, a later change could gate the parse to PostgreSQL and drop SQLite without anyone noticing.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, applied your suggestion as written in 8936117. I also added
parse_on_conflict_target_predicatetotests/sqlparser_sqlite.rs, so restricting the parse to PostgreSQL would fail a test rather than only contradict the doc.I checked it against SQLite 3.37.2 as well. With a partial unique index on
t (a) WHERE b > 0,INSERT INTO t VALUES (1, 2, 3) ON CONFLICT (a) WHERE b > 0 DO NOTHINGruns, and the second insert is a no-op.ON CONFLICT WHERE b > 0is a syntax error.