Found during the production-readiness investigation.
Symptoms / failure scenarios:
- Schema is introspected once in
setup_postgres and never refreshed. After ALTER TABLE ... ADD COLUMN, parse_cols silently drops the new column from every envelope (apps/engine/src/replication.rs:447-449) — synced rows are missing the column until an engine restart, with no error.
TRUNCATE produces no envelopes — it only logs (replication.rs:269-276). Truncated rows linger forever in every shape, aggregate, and subquery inner set.- A
REPLICA IDENTITY regression (e.g. a migration recreated the table) degrades to forwarding new-only updates and skipping deletes (replication.rs:231-265) — shapes keep phantom rows.
In all three cases we keep serving wrong data quietly. Upstream invalidates affected shapes (409 → client refetch) and runs a 60s SchemaReconciler sweep to catch silent DDL.
Fix direction: periodic re-introspection diffed against the registered schema; on change, TRUNCATE, or replica-identity regression → invalidate affected shapes (drop + refetch signal), never degrade silently. (Moving to pgoutput later provides relation messages for free.)
🤖 Generated with Claude Code
Found during the production-readiness investigation.
Symptoms / failure scenarios:
setup_postgresand never refreshed. AfterALTER TABLE ... ADD COLUMN,parse_colssilently drops the new column from every envelope (apps/engine/src/replication.rs:447-449) — synced rows are missing the column until an engine restart, with no error.TRUNCATEproduces no envelopes — it only logs (replication.rs:269-276). Truncated rows linger forever in every shape, aggregate, and subquery inner set.REPLICA IDENTITYregression (e.g. a migration recreated the table) degrades to forwarding new-only updates and skipping deletes (replication.rs:231-265) — shapes keep phantom rows.In all three cases we keep serving wrong data quietly. Upstream invalidates affected shapes (409 → client refetch) and runs a 60s
SchemaReconcilersweep to catch silent DDL.Fix direction: periodic re-introspection diffed against the registered schema; on change, TRUNCATE, or replica-identity regression → invalidate affected shapes (drop + refetch signal), never degrade silently. (Moving to pgoutput later provides relation messages for free.)
🤖 Generated with Claude Code