fix: CHECKPOINT DuckDB after finishing writing #72
+16
−1
Conversation
This file contains 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
sgrebnov
approved these changes
Aug 26, 2024
phillipleblanc
approved these changes
Aug 26, 2024
Sevenannn
approved these changes
Aug 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🗣 Description
CHECKPOINTfor DuckDB after finishing writing. This flushes the Write-Ahead Log to the database.This is a requirement for connections that have attachments configured, observed on Linux. Without flushing the write-ahead log, the log file locks to the writer process. This prevents the reader from reading the WAL file, causing query errors due for
Failure while replaying WAL file.