Skip to content

Take over a stopped PHP PostgreSQL database backup-first - #533

Merged
rmcdaniel merged 94 commits into
rust-325-sqlite-takeoverfrom
rust-325-postgres-takeover
Oct 20, 2026
Merged

rmcdaniel merged 94 commits into
rust-325-sqlite-takeoverfrom
rust-325-postgres-takeover

Conversation

@rmcdaniel

Copy link
Copy Markdown
Member

Part of #325: the backup-first in-place upgrade gate. Stacked on #532 (which sits on #529 and #523); review those first. Implements the PostgreSQL part of the design in #517.

Takeover

upgrade-takeover now also accepts DB_CONNECTION=pgsql, with the owner's DB_* settings. One read-committed transaction:

  1. Takes native's bootstrap advisory key, so no native node can open the database meanwhile.
  2. Locks every public table in ACCESS EXCLUSIVE mode. The later DDL needs that mode anyway, so no lock is upgraded while another session waits. A session still holding a table after native's 5 s lock wait refuses the takeover with upgrade_source_in_use.
  3. Runs the inventory, queue and payload inspections and recomputes the fingerprint inside that transaction, refusing unless it equals DW_UPGRADE_BACKUP_FINGERPRINT.
  4. Adds the native relations, converts the recorded PHP release layout, records the native migration and runs native's startup verification (marker, ledger and full catalog), then commits.

PHP's added columns are each table's last, so dropping them leaves every remaining column at its position, and the catalog check passes.

The layout conversion and the ledger record are now shared by SQLite and PostgreSQL through the Backend trait. The PostgreSQL inspection and fingerprint can run inside the caller's transaction (postgres_inventory, postgres_digest). Fingerprint reads are no longer cut off by the 30 s inspection statement limit: like MySQL's, they are bounded by the client deadline, so large tables can be fingerprinted.

Interruption

A takeover killed before its commit leaves nothing committed. It is rerun with the same digest.

  • PostgreSQL: the server ends the killed session's transaction and locks.
  • SQLite: the killed run leaves a rollback journal. Read-only inspection still refuses it (upgrade_source_sqlite_journal_unqualified). The writable takeover open now lets SQLite roll the journal back, and the fingerprint check then proves the file is the backed-up one.

Checks

  • PostgreSQL qualification tests (runtime::postgres::tests::qualification_takeover_*, run by the postgres-storage job):
    • A PHP 2.9.7-shaped database is converted and opened by native, and a second takeover is refused as upgrade_source_already_owned.
    • The frozen layout is taken over.
    • Each of these is refused with the catalog and every row unchanged: a wrong digest, a malformed digest, a session holding jobs, a write after the backup, a service call, and an external payload.
    • A real takeover process SIGKILLed just before its commit leaves the source unchanged, and the rerun succeeds.
  • SQLite unit test: the same SIGKILL test, ending in a successful rerun.
  • Upgrade source cohort: the PostgreSQL job now takes over a restored copy of the published-PHP source, starts native on it and resumes the originals, as the SQLite job does. Its timer is short for that reason.
  • Local results:
    • The 4 new PostgreSQL tests and all 11 PostgreSQL qualification tests pass.
    • SQLite lib tests pass (128), as do the upgrade tests (41).
    • The cohort passed on PostgreSQL and SQLite for both the default (PHP 2.8.0 layout) and the PHP 2.9.7 sources. In each run, the leased activity completed on its original attempt, the stale task got 409 task_not_leased, the timer fired 0.07–0.17 s after its deadline, both workflows completed and PHP refused with php_database_refused.

Not covered yet

  • MySQL and MariaDB takeover. LOCK TABLES refuses to create or drop tables it does not hold, so they need the design's session check and step journal.
  • Nested payload columns the inspection does not scan yet.
  • Takeover with external payloads or service calls.
  • Multi-node qualification.

The report keeps stored_representation_compatibility_verified: false.

🤖 Generated with Claude Code

durable-workflow-ops and others added 30 commits October 20, 2026 03:22
Five transitions run Avro work while holding the global transition lock:
the rejected-signal command, signal arguments applied by a resumed task,
cooperative cancellation requests, task repair and fenced deregistration.
They shared the single codec permit with describe, query and listing
reads, so under read load a transition waited on the lock for unrelated
decodes. A per-call-site probe on the CPU deadline-health cell measured
0.58 to 0.80 s of such waiting in a cancellation request.

These transitions now take a separate transition_codec permit. Reads keep
signal_codec. Encodings, values and refusals are unchanged.

New tests hold the read permit and require a cancellation request, a
signal-resumed completion, a fenced deregistration and a range repair to
finish within one second. They time out with the old wiring.

Part of #325.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The worker protocol requires poll_status "leased" on a workflow task
claim, and published PHP (2.5.14 and 2.8) reports "leased" and "empty"
for workflow, activity and query polls alike. Native reported "task" and
"timeout". It now reports the same two values. The wake hint
task_queue_changed and every refusal status are unchanged.

The cross-kind poll contract, which accepted either claim status, now
requires "leased".

Part of #325.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each held native poll used to repeat its full claim every 50 ms: a
transaction under the global transition lock that read the registration,
deleted expired poll receipts and selected candidates. With no work, idle
cost grew by about 0.035 cores per waiting poll, two-thirds of it in MySQL,
and every probe queued behind, and delayed, real transitions.

A held poll now claims under the lock on its first probe. Afterwards it
claims only when a lock-free read finds something it could claim or must
refuse: an eligible task or query, a receipt for its own poll request, or a
removed, moved or replaced registration. The read runs at once when a commit
on the same node wakes the poll, and otherwise every 50 ms, which is how a
poll still observes other server processes. A false positive costs one empty
claim, and a commit racing a read is seen on the next read.

New tests hold the transition lock from outside the runtime and check that
idle workflow, activity and query polls still end at their deadline (each
fails with the previous probing), and that a held poll still claims a task
or query, and refuses a removed registration, committed by another node.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The published PHP SQLite reference shares its database file with its
maintenance loop and sometimes refuses a request with its documented HTTP 503
backend_lock_pressure reply: retryable, nothing committed, worker mutations
fenced by task and attempt. Probe runs failed on these refusals for polls,
worker operations and a Rust SDK actor's deregistration.

- Parity probes now build their SDK clients through parityClient(), whose
  default transport is the SDK's own Psr18Transport over Guzzle with an
  innermost retry middleware. The transport keeps every capability the SDK
  checks (bounded requests and payload transfer), unlike the earlier
  wrapper. Observed-transport stacks add the same middleware innermost, so
  recording middleware sees only the final reply.
- lockPressureOperationRetryDelay retries any non-poll request only on
  status 503, reason backend_lock_pressure and retryable true, within 15
  retries, 30 s of waiting and the request's own timeout. Polls keep the
  stricter rule that no task was handed out. Bodies that cannot be replayed
  are never retried. Retries are reported once on stderr.
- The Rust SDK actor retries its deregistration on the same refusal, under
  the same bounds.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
On the October 20 profile host, lock-free reads every 50 ms cut MySQL's
idle cost at 24 waiting polls only from about 0.53 to 0.46 cores, and the
native process stayed near 0.28 cores. The cost is the read rate, 20 per
second per poll, not the lock.

A held poll now reads 50 ms after a probe and then at doubling intervals up
to 250 ms. A same-node wake still reads at once and starts again from 50 ms,
so same-node work is unaffected, and work committed by another server
process is observed within 250 ms. No wait runs past the poll's deadline.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The task read now sits next to the task claim in store.rs and the query
read next to the query claim in queries.rs, inside their existing Store
impls. poll_readiness.rs keeps only the read pacing. No behavior changes.

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>
The parity jobs write Rust test output to evidence files, so a failed
cargo test left only its exit code in the step log. An ERR trap now prints
the panics and the failed test names from those files.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
durable-workflow-ops and others added 28 commits October 20, 2026 13:33
This probe retries lock-pressure poll refusals itself and records each
retry, while a recording proxy outside the client logs every refused poll.
Retrying below the SDK hid those retries from the probe, so the contract
found a refused poll without its recorded retry. The probe keeps its plain
client.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With no lock wait, a writer that had just closed could still hold its lock
when the preparation opened the file, and the preparation refused it as in
use. A two-second wait covers that; a file another process keeps open is
still refused.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…atures

The upgrade source author now also writes a third original: a workflow that
opens a signal wait, then receives its declared signal under published
PHP, whose resume task stays unclaimed. After the takeover, native must
deliver that signal from PHP's rows: the resumed task keeps the original
history and the signal's PHP-written arguments, and the workflow
completes. The resume accepts the three originals in any order.

The payload inspection now also checks the codec-tagged payloads of
workflow commands, signal records and updates.

Takeover refuses a source holding rows of a published PHP feature native
does not implement yet (runtime credentials, message streams, service
definitions, update validation tasks, worker sessions, build ID rollouts
and search attribute definitions), rather than leaving them unread.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Give codec work under the transition lock its own permit
The upgrade source author adds a fourth original whose worker stops after
claiming its workflow task. PHP's lease on that task expires after the
takeover. Native must then redeliver the same task as its next attempt,
refuse the expired PHP attempt's completion, and complete the workflow on
its original history.

Part of #325.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…volution-518

Allow replay-compatible workflow definition upgrades and explain routing
Two alternating PHP/native pairs on a second dedicated host repeat the
morning's matched comparison on main after #516. Native meets or beats PHP
in every window, with no drift within any run. PHP's own capacity at 1/s
differs between the two hosts, which the observations record.

Part of #325.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ssure

Retry the PHP reference's lock-pressure refusals in parity probes
…try-safety

Prepare Server 2.9.9 entry-safety release
Record two repeated matched PHP/native pairs after #516
…e 2.9.7 cohort

Public history now lifts each command's principal onto its event, and worker
task history has none, so the recovered terminal resumption compares the
fields both views share. The SQLite PHP 2.9.7 upgrade cohort steps set the
job's resource scope like their neighbours; the cleanup step failed without
it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Resume a PHP-accepted signal after takeover and refuse unsupported features
Prepare a PHP SQLite source in WAL mode for the upgrade commands
Take over a stopped PHP MySQL or MariaDB database in recorded steps
@rmcdaniel
rmcdaniel merged commit b2e88bb into rust-325-sqlite-takeover Oct 20, 2026
8 of 9 checks passed
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.

2 participants