Optimize MERGE INTO DELETE RETURNING by passing columns through from scan #10
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.
This PR optimizes MERGE INTO DELETE RETURNING by passing physical columns through from the scan instead of fetching them by row ID in the fallback path.
Changes
delete_return_columnsvector toLogicalMergeIntoto map physical columns to their positions in the projectiondelete_return_columnsinbind_merge_into.cppwhen RETURNING is used with a DELETE actionContext
This optimization mirrors the approach used in regular DELETE RETURNING (PR duckdb#20485) but extends it to MERGE INTO statements. Previously, MERGE INTO DELETE RETURNING would fall back to fetching columns by row ID, which is slower than passing them through from the scan.
Testing