PostgreSQL Replication Recovery

Predict replication recovery and rank throttling, promotion or rebuild actions.

Prediction improvement95.27%

Planning top-1100%

Critical violations0

Runtime p950.52 ms

Training sourceA08 PostgreSQL replication simulator v0.1

Training transitions3,200

Held-out one-step error0.45%

Held-out improvement94.13%

Interactive package

Change the context. Compare the plans.

The local runtime evaluates candidate control sequences, predicts their trajectories and rejects plans outside the declared envelope.

Live runtime

Plan from system state

Goal

Observed stateValues observed at H0

WAL generation rateMB/s

MB/s

Replay lags

Retained WALGB

Primary load%

Replica healthscore

score

Planner search7 candidates · H6

ObserveThrottle writesPrioritize replicaPromote replicaDrop stale slotRebuild replica

Set the current telemetry, choose a goal and run the planner.

Results include actions, predicted state and constraint checks.

World contract

One PostgreSQL primary and two streaming replicas during a bounded lag or failover event.

Temporal unit: 30_seconds. Supported horizons: 1, 4, 8.

State

WAL generation rate0 to 300 MB/s

Replay lag0 to 180 s

Retained WAL0 to 1200 GB

Primary load0 to 100 %

Replica health0 to 1 score

Actions

Observeobserve

Throttle writesthrottle writes

Prioritize replicaprioritize replica

Promote replicapromote replica

Drop stale slotdrop stale slot

Rebuild replicarebuild replica

Goals

Restore replication4 declared targets

Constraints

replica viabilitycritical · gte 0.45

wal capacitycritical · lte 1050

primary saturationhard · lte 96

Package record

Everything required to inspect and run this world.

Package digestsha256:db2be24e1dd898d31340c03fea5ce2b2bd8d4273dcbb9059e55d52ca3cd4a8bd

world.jsonScope, lineage and runtime contract

model artifact285 parameter transition profile

schemas/State, action and goal validation

eval/40 registered cases and result digest

Declared limitationsSimulation-trained on a bounded primary-replica topology and synthetic workload traces.No SQL semantics, storage hardware or synchronous quorum model.Promotion and slot actions require independent operator review.