alloydb-omni-replication

Monitor PostgreSQL replication health and audit publication tables in AlloyDB Omni.

2|1|Updated May 25, 2026

Search Tags:#monitoring #database #postgresql #replication #wal #alloydb

Ready to run

npx skills add https://github.com/interflownex/All-in-One --skill alloydb-omni-replication

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: alloydb-omni-replication
Source: https://github.com/interflownex/All-in-One/tree/main/.gemini/skills/alloydb-omni-replication
Command: npx skills add https://github.com/interflownex/All-in-One --skill alloydb-omni-replication

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @toolbox-sdk/server, and includes scripts (resource) components.

What problem does it solve?

This Skill addresses the complexity of maintaining distributed PostgreSQL database clusters by providing automated visibility into replication health, synchronization states, and publication configurations.

Core Features & Use Cases

Replication Health Monitoring: Track replica lag, connection status, and WAL slot sizes to ensure data consistency across nodes.
Publication Auditing: Easily list and filter publication tables and schemas to verify data distribution setups.
Use Case: Use this tool to diagnose a replication delay by checking the total lag and identifying which specific replication slots are holding up WAL removal.

Quick Start

Use the alloydb-omni-replication skill to list all active replication slots and their current WAL lag status.

Frequently Asked Questions about alloydb-omni-replication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check PostgreSQL replication slot lag in AlloyDB Omni?▼

To check PostgreSQL replication slot lag in AlloyDB Omni, you can monitor replica lag, connection status, and WAL slot sizes. This Skill retrieves performance metrics to diagnose delays and identify specific slots holding up WAL removal.

How does WAL retention affect distributed PostgreSQL database synchronization?▼

WAL retention affects synchronization by keeping transaction logs until replicas consume them. If replication slots fail to process WAL promptly, the logs accumulate, holding up WAL removal and causing replica lag across distributed PostgreSQL nodes.

Do I need the toolbox server package to monitor AlloyDB Omni replication?▼

Yes, you need the @toolbox-sdk/server package to monitor AlloyDB Omni replication. This Skill requires it to execute administrative database queries and retrieve the performance metrics needed for health monitoring.

How do I audit publication tables and schemas for PostgreSQL replication?▼

To audit publication tables and schemas for PostgreSQL replication, use this Skill to list and filter publication configurations. This verifies your data distribution setups and ensures publication tables are correctly aligned across nodes.

Why does my PostgreSQL replication slot hold up WAL removal?▼

A PostgreSQL replication slot holds up WAL removal when a replica is disconnected or lagging behind. This Skill helps diagnose the delay by checking total lag and identifying which specific replication slots are preventing WAL cleanup.