PostgreSQL replication keeps your data safe and your read replicas up to date.
But replication issues can cause:
- Data loss if slots fall too far behind
- Disk space exhaustion from WAL retention
- Increased XID age preventing vacuum
PG Pilot monitors all replication slots to ensure they stay healthy:
- Physical slots: For streaming replication to standby servers
- Logical slots: For logical replication and CDC tools
What it monitors
- Replication slot active/inactive status
- Replication lag in bytes
- WAL status (reserved, extended, unreserved, lost)
- Slot type (physical/logical)
- XMIN age for each slot
- Catalog XMIN age
How to use
Navigate to the Replication section from the main navigation.
Slot Overview
See all replication slots with:
- Active/inactive status indicator
- Current lag (formatted as bytes/KB/MB/GB)
- WAL status badge
- Slot type (physical/logical)
Health Indicators
Color-coded status:
- Green: Active slot with minimal lag
- Yellow: Warning (high lag or old XMIN)
- Red: Critical (inactive slot or lost WAL)
Slot Details
Click a slot to see:
- Detailed lag metrics
- XMIN and catalog XMIN ages
- Consumer information
- Recommendations for issues
Alerts
PG Pilot alerts when:
- Slots become inactive
- Lag exceeds thresholds (1GB warning, 5GB critical)
- XMIN age becomes problematic
- WAL status changes to unreserved or lost