You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* docs(plan): warmer hardening plan (#65)
* refactor(warmer): consolidate MAX(tid) query + log/skip on failure (#65)
Add module-level _read_max_tid(conn) helper and a public
PGJsonbStorage.current_max_tid() method that logs on failure and
returns None. Route _restore_state, poll_invalidations, and the
warmer's load_current_tid_fn through them. Warmer skips warmup
when current_max_tid returns None instead of installing consensus=0.
Closes I1 and I2 of #65.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* refactor(instance): hoist _read_max_tid import to module top (#65)
Matches the existing import-style block (6 other names from .storage
already imported at module top). Avoids a per-call name lookup in
the poll_invalidations hot path.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(shared-cache): consensus_tid property + set() returns bool (#65)
Both are wanted by the cache warmer's race-detection fix (next
commit). The existing instance.load / load_multiple call sites
ignore the new return value; no behaviour change there.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(warmer): recover from consensus race; warn on zero accepted writes (#65)
Closes I3 of #65. After poll_advance, re-read consensus_tid and use
that as the polled_tid for subsequent set() calls — if another
instance advanced consensus ahead of our sampled TID, this ensures
our sets still pass the gate. Track accepted vs. attempted writes
via the new set() return value; log a WARNING when the entire
warmup was rejected despite non-empty results.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test(shared-cache): pin main-storage _finish → shared.poll_advance (#65)
Coverage gap flagged in #63 final review. Pins the invariant that
the direct-use write path advances consensus and invalidates
changed zoids in the shared cache, independent of any instance's
tpc_finish.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: CHANGES entry for 1.12.1 warmer hardening (#65)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments