Repository navigation
chore: vendor latest bedrock (52082d4b80) - #61
Merged
Merged
Conversation
Move the bundled SQLite from bedrock 2137918d6a (2026-08-10) to 52082d4b80 (2026-11-09, reports 3.55.0). This picks up the wal2 fix for the writer/checkpointer race (4bc8fdd581): when a COMMIT switches wal files, a checkpointer taking a lock in the gap could make the writer return a spurious SQLITE_BUSY. See https://sqlite.org/forum/forumpost/63ba0208a6 Also included: - SQLite 3.54.0 and 3.54.1 - most fixes queued for 3.54.2, including two WAL/shm recovery race fixes, a b-tree cursor cell-cache fix, ALTER TABLE DROP COLUMN leaving a stale index, and several wrong-result query fixes Only CHECKIN in deps/download.sh and the regenerated deps/sqlite3/* change.
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
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.
Summary
Update the vendored SQLite from bedrock
2137918d6a(2026-08-10) to52082d4b80(2026-11-09).SQLITE_VERSIONgoes from 3.54.0 to 3.55.0.The reason is the upstream fix for a wal2 bug: when a
COMMITswitcheswal files,
walRestartLog()releases its exclusive locks and then takesa shared lock on the new file. A checkpointer that locks the file in that
gap makes the shared lock fail, and
COMMITreturns a spuriousSQLITE_BUSYthatbusy_timeoutdoesn't cover. Upstream fixed it inwal2 check-in
4bc8fdd581, which was merged into bedrock as52082d4b80. Forum report:https://sqlite.org/forum/forumpost/63ba0208a6
This lets zero-cache drop its
COMMITretry workaround(rocicorp/mono-internal#372).
What else comes with it
Bedrock has had no check-ins since the merge. The seven trunk merges
between the old pin and this one bring in:
cycles on SQLite's benchmark).
SQLITE_READONLY_RECOVERYor
SQLITE_READONLY_CANTINIT-shmcontent copied during recovery is now always initialisedALTER TABLE DROP COLUMNcould leave a stale indexJOIN, vector
NOT INwith a DESC index, and compound SELECTs withCOLLATE
Not included (not yet merged into bedrock): a Nov 3 ORDER BY/collation
fix and a Nov 12 incremental-blob fix (zero-sqlite3 doesn't expose
incremental blobs).