Repository navigation
Design the backup-first native takeover - #517
Merged
Merged
Conversation
The storage audit lists the takeover gates, and the inspection commands keep their backup, quiescence, compatibility and takeover flags false. This note proposes what turns each one true: - a fingerprint of the database's complete logical contents, compared between the stopped source and a restored backup, then checked again inside the takeover's own exclusive transaction before the marker is written; - per-backend writer exclusion and atomicity, with a marker step journal where DDL commits implicitly; - resumption of an interrupted takeover from the marker, refusal of a different fingerprint, and the per-backend upgrade fixtures and checks. It records what is not yet known, such as MySQL's exclusion method. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 20, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 20, 2026
PHP grants queue_delivery_reference no task authority, and the queue inspection already binds every queued job to its task row, so the conversion removes the column and reports how many references it held. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PostgreSQL locks every table in ACCESS EXCLUSIVE mode after native's bootstrap key, since the later DDL needs that mode anyway. On SQLite and PostgreSQL the marker commits with everything else, so an interrupted takeover is simply rerun; only MySQL and MariaDB need the step journal. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 20, 2026
MySQL and MariaDB use native's bootstrap lock and a session check rather than LOCK TABLES, which refuses to create or drop tables it does not hold. Their journal is a rust-takeover row in native's marker table. A SQLite source in PHP's default WAL mode is first switched to the rollback journal with upgrade-prepare-sqlite. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
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.
Part of #325: the backup-first in-place upgrade gate.
The storage audit lists the upgrade gates, and the merged inspection commands (#460) keep
backup_verified,php_quiescence_verified,stored_representation_compatibility_verifiedandtakeover_allowedfalse. This addsdocs/rust-server-upgrade-takeover.md, a design input (not a contract change or a qualified procedure) for what turns each one true:takeover. A rerun with the same fingerprint resumes after the last recorded step; a different fingerprint is refused.Implementation follows in separate PRs, SQLite first.
🤖 Generated with Claude Code