PostgreSQL replication

Start Here

Manual Home Installation Windows Installation Linux Engine Container Linux Console Container Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Mode Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Performance History Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

Legacy Documentation

PostgreSQL Replication shows the monitored server's replication role, visible standbys, replication slots, WAL/archiver signals, and replica conflict evidence.

What to review

Server role and topology.
Connected standbys from pg_stat_replication.
Replication slot activity and retained WAL.
Replay lag where available.
Archiver failures and WAL archiving rate.
Replica conflict counters.

Workflow

Open the PostgreSQL server in the navigation tree.
Select Replication.
Review the summary pills for role, connected standbys, slots, replay lag, retained WAL, archiver failures, and conflicts.
Use the topology strip to confirm which standby connections are visible to the monitored server.
Review Standbys, Replication Slots, Archiver, and Replica Conflicts tabs for detail.

How to interpret replication signals

On a primary server, missing standbys, inactive replication slots, increasing retained WAL, and replay lag are the main signals to investigate. Retained WAL can fill disk even when the primary itself is otherwise healthy.

On a standby server, WAL receiver and conflict counters can explain why replay is delayed or why read queries are being cancelled. Some cloud providers restrict access to replication views, so missing rows may mean a permission or platform limitation rather than no replication.

Alerts

Mini DBA can raise PostgreSQL alerts for connected standby count, inactive replication slots, replication lag, and replication-slot retained WAL. Use the Replication page to inspect the source evidence behind those alerts.