[Fix] Reset segment memory when initialising new Prefix#18441
Merged
Mytherin merged 1 commit intoduckdb:v1.3-ossivalisfrom Jul 30, 2025
Merged
[Fix] Reset segment memory when initialising new Prefix#18441Mytherin merged 1 commit intoduckdb:v1.3-ossivalisfrom
Mytherin merged 1 commit intoduckdb:v1.3-ossivalisfrom
Conversation
Collaborator
|
Thanks! |
github-actions bot
pushed a commit
to duckdb/duckdb-r
that referenced
this pull request
Jul 30, 2025
[Fix] Reset segment memory when initialising new Prefix (duckdb/duckdb#18441) [Chore] Tidy test configs (duckdb/duckdb#18426)
github-actions bot
added a commit
to duckdb/duckdb-r
that referenced
this pull request
Jul 30, 2025
[Fix] Reset segment memory when initialising new Prefix (duckdb/duckdb#18441) [Chore] Tidy test configs (duckdb/duckdb#18426) Co-authored-by: krlmlr <krlmlr@users.noreply.github.com>
2 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When making changes to indexes, we might reuse previously used index segments. In the case of this bug, we reuse a previous segment in a place where we then expect it to be uninitialised.
I am not sure how to add the reproducer, since the table (with the correct sequence of values to cause this) is 10MB (compressed, all other columns removed).
Fixes #18190