Logical Replication

Catch replication drift before it costs you data

Slot health, subscription state, apply lag, WAL retention, and PG17 conflict detection — all in one place.

Most monitors stop at streaming replication. Logical replication is where real incidents hide: inactive slots eating disk, subscriptions stuck in copy, publications missing tables, apply lag creeping up until cutover day.

Slot and subscription inventory

See every publication, subscription, slot, and replication origin in one place — across primaries and replicas. Know what is replicating where without SQL spelunking.

WAL retention alerts

An inactive slot will quietly eat your disk. MyDBA alerts on WAL retained per slot before you run out of space — with the slot name and retention age to act on.

Apply lag per subscription

Track apply lag end-to-end per subscription. Correlate spikes with source-side load, network blips, or conflicts — not just "the replica is slow".

PG17 conflict detection

Postgres 17 exposes replication conflict state in the catalog. MyDBA surfaces collected conflict information alongside replication metrics. Visibility depends on collection frequency and PostgreSQL version.

10 dedicated health checks (L0–L10)

From slot state and WAL retention through to apply lag, table sync, subscription state, and PG17 conflict resolution — every known failure mode, scored.

Table sync progress

Watch the initial copy phase for every table in every subscription. Get alerted if a worker is stuck, has errored, or has not made progress in N minutes.

Historical trend

Apply lag, WAL retention, and slot state are stored as time series. Catch patterns — "lag climbs every Monday at 9am" — that point-in-time views hide.

Correlated with workload

See lag alongside query latency, vacuum activity, and connection count on the same page. Replication doesn't fail in isolation.

Works with pglogical too

Built-in logical replication and pglogical are both supported. Same UI, same alerts, same timeline.

10 logical replication health checks

Every known failure mode is scored and prioritised alongside the rest of your health check results.

L0Replication slots present and active
L1Inactive slot detection (disk risk)
L2Lost slot detection (requires re-sync)
L3WAL retention per slot within limits
L4Subscription enabled and connected
L5Table sync workers making progress
L6Apply lag inside acceptable bounds
L7Publication tables in sync with subscription
L8Replication origin progress
L9Conflict resolution settings (PG17+)
L10Active conflict detection (PG17+)

Related capabilities

See it in action

Start free with one primary or standalone PostgreSQL instance and all its databases. Monitoring, alerts, query insights, index advice, team access and every non-AI feature included. No replicas. No credit card required. New Free connections get seven days of full collection, then reduced sampling. Free and Pro include 30 days of monitoring history.