Backport revert append fixes #19941
Merged
Backport revert append fixes #19941
Conversation
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
github-actions bot
pushed a commit
to duckdb/duckdb-r
that referenced
this pull request
Nov 27, 2025
Backport revert append fixes (duckdb/duckdb#19941)
github-actions bot
added a commit
to duckdb/duckdb-r
that referenced
this pull request
Nov 27, 2025
Backport revert append fixes (duckdb/duckdb#19941) Co-authored-by: krlmlr <krlmlr@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In #19937 I fixed an issue with
RevertAppendpotentially leaving the segment tree in an undefined state in certain situations (when we would truncate at exactly the row group boundary). This method is called when a unique / primary key constraint violation is found during the commit process. This could then cause issues to happen in subsequent code. This PR backports the fix for this to v1.4.