Skip to content
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

Fix #10982 - only update total rows of row group collection after we finish appending to prevent other readers from attempting to initialize scans on in-progress appends #11011

Merged
merged 3 commits into from
Mar 6, 2024

Conversation

Mytherin
Copy link
Collaborator

@Mytherin Mytherin commented Mar 6, 2024

Fixes #10982

This was an issue that could sporadically happen if multiple connections were concurrently writing and reading from the same table. Essentially we updated the total number of rows in the table before adding the column segments containing the data - which could then lead to an exception being thrown when reading as another connection would try to read until total_rows, but could not find the column segment belonging to those rows.

Mytherin added 3 commits March 6, 2024 09:57
…er we finish appending to prevent other readers from attempting to initialize scans on in-progress appends
@Mytherin Mytherin merged commit 0c1d807 into duckdb:main Mar 6, 2024
43 checks passed
github-actions bot pushed a commit to duckdb/duckdb-r that referenced this pull request Mar 16, 2024
Merge pull request duckdb/duckdb#11011 from Mytherin/concurrenttableinsertion
@Mytherin Mytherin deleted the concurrenttableinsertion branch July 5, 2024 11:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Could not find node in column segment tree!
1 participant