Repository navigation
feat(deploy): control shared PostgreSQL schema maintenance and recovery - #846
Merged
Merged
Conversation
LIghtJUNction
marked this pull request as ready for review
October 11, 2026 23:04
|
You have reached your Codex usage limits for security reviews. Please try again later. |
This was referenced Oct 11, 2026
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.
The latest backend needs an updated PostgreSQL schema, while the running providers seal the complete current catalog. Add a dedicated schema-only maintenance path that preserves financial rows and old table/index identities, then creates honest post-upgrade recovery capsules before the normal combined backend/frontend transaction.
The native controller closes admission, drains and stops both writers, retains three deployment locks, verifies an encrypted backup through a full isolated restore, and runs DDL once in a single transaction. Canonical receipts bind the owner, preserved-data outcome, recovery hooks and process generations. Pre-claim abort and dead-daemon recovery before worker execution restore unchanged providers; uncertain mutations are reconciled without replaying DDL or sweeping unknown ownership.
Validation: full local Go 1.25.1 suite passed at d259dd2. The final 67818a6 delta is confined to the deployment CLI; application, schema/model, guardian script and publisher objects are identical. Final Go 1.25.1 deployment CLI/app CLI/fence race tests with disposable PostgreSQL passed (52.051s). Separate qualifications cover encrypted full restore, preserved schema/data, negative owner/type cases and original guardian continuity. Evidence recorder tests and formatting checks passed.
Production remains Go 0.2.111 / Web 0.1.145. Go112 publication and actual isolated systemd installation/recovery validation follow this merge; production DDL requires the completed caller and that validation. This path uses a maintenance window and does not claim zero downtime.