Add guarded atomic primitive-life publication (M11.2c-2c)
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m54s
Foundation / checks (client) (push) Successful in 12m21s
Foundation / checks (network) (push) Successful in 13m52s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (tsan) (push) Canceled after 2m34s
Foundation / checks (postgres) (push) Canceled after 6m8s
Foundation / checks (checks) (push) Canceled after 18m34s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m54s
Foundation / checks (client) (push) Successful in 12m21s
Foundation / checks (network) (push) Successful in 13m52s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (tsan) (push) Canceled after 2m34s
Foundation / checks (postgres) (push) Canceled after 6m8s
Foundation / checks (checks) (push) Canceled after 18m34s
This commit is contained in:
@@ -77,7 +77,13 @@ Local checks do not close ADR-0097's reference-worker qualification.
|
||||
- 11.2c-2b: portable primitive checkpoint profile 3, history profile 2, complete
|
||||
payload closure and bounded birth traces. SQL admission remains disabled until
|
||||
guarded publication atomically binds bodies and reservations.
|
||||
- 11.2c-2 and 11.2d remain: atomic funded checkpoint publication, reconciliation,
|
||||
host/session integration and crash-boundary qualification.
|
||||
- 11.2c-2c: schema v16 guarded primitive publication atomically validates control,
|
||||
reservations and birth bindings with the checkpoint head. Exact retries
|
||||
converge, conflicting evidence and stale control refuse, and runtime can read
|
||||
immutable life bindings. Full PostgreSQL migrations, process, recovery,
|
||||
backup/restore, host-loss, upgrade and privilege checks pass.
|
||||
- Remaining 11.2c/d: C++ durable publication/object-store adapter, primitive-life
|
||||
region recovery/host and explicit session protocol integration, plus crash-boundary
|
||||
qualification. Schema admission alone does not make profile 3 hostable.
|
||||
|
||||
No deployed world has been provisioned or changed by this work.
|
||||
|
||||
@@ -5601,3 +5601,22 @@ and both lifecycle/checkpoint tests passed. The revised encoder was rechecked wi
|
||||
ASan+UBSan (both tests), clang-tidy/format, and Windows Release 62/62. WSL temporary
|
||||
logs disappeared after process exit; the reproduced build log was retained under
|
||||
`build/m112-profile-callers.log` instead.
|
||||
|
||||
## 2026-10-10 — M11.2c-2c schema v16 guarded publication
|
||||
|
||||
Executed the GCC 14 Release `evo-postgres-tests` build and complete
|
||||
`tools/ci/postgres-check.sh` against PostgreSQL 18.6. This includes the new
|
||||
primitive publication integration (reservation/control checks, changed and exact
|
||||
retry behavior, rollback and concurrent retries), every existing process and
|
||||
recovery integration, schema upgrade/checksum/privilege audits, backup/restore,
|
||||
host-loss and failed-upgrade rehearsals. The full command passed. A prior run
|
||||
correctly reported the historical v3 fixture had 16 migration rows while the
|
||||
script still expected 15; the expectation was updated and the complete run then
|
||||
passed. The focused publication/concurrency lane also passed after the fixture
|
||||
used commit IDs unique across this shared test database.
|
||||
|
||||
No production world was provisioned or altered. This segment adds SQL profile
|
||||
admission and a runtime binding read, but not the C++ object-store publication
|
||||
adapter or primitive-capable server recovery/session path. Do not interpret its
|
||||
green database gate as end-to-end life recovery. Full C++ unit/network/QUIC lanes
|
||||
were not rerun because this segment changes no replicated network type.
|
||||
|
||||
Reference in New Issue
Block a user