with one click
alloydb-omni-replication
// Use these skills when you need to monitor the health of database replication, manage sync states between nodes, and audit publication tables for distributed setups.
// Use these skills when you need to monitor the health of database replication, manage sync states between nodes, and audit publication tables for distributed setups.
Use these skills when you need to manage user roles, inspect permissions, and verify security-related configuration parameters.
Use these skills when you need to explore the database structure, identify schema objects like views and triggers, and execute SQL queries to interact with your data.
Use these skills when you need to audit database health, identify storage bloat, find broken indexes, and verify tablespace or maintenance configurations.
Use these skills when you need to troubleshoot production issues by identifying locks, tracking long-running transactions, and getting a high-level view of server state.
Use these skills when you need to fine-tune the database engine settings, manage extensions, or optimize the columnar engine for better analytical performance.
Use these skills when you need to analyze query performance, generate execution plans, check table/column statistics, and monitor overall database activity.
| name | alloydb-omni-replication |
| description | Use these skills when you need to monitor the health of database replication, manage sync states between nodes, and audit publication tables for distributed setups. |
All scripts can be executed using Node.js. Replace <param_name> and <param_value> with actual values.
Bash:
node <skill_dir>/scripts/<script_name>.js '{"<param_name>": "<param_value>"}'
PowerShell:
node <skill_dir>/scripts/<script_name>.js '{\"<param_name>\": \"<param_value>\"}'
Note: The scripts automatically load the environment variables from various .env files. Do not ask the user to set vars unless skill executions fails due to env var absence.
Fetches the current state of the PostgreSQL server, returning the version, whether it's a replica, uptime duration, maximum connection limit, number of current connections, number of active connections, and the percentage of connections in use.
| Name | Type | Description | Required | Default |
|---|---|---|---|---|
| table_names | string | Optional: Filters by a comma-separated list of table names. | No | |
| publication_names | string | Optional: Filters by a comma-separated list of publication names. | No | |
| schema_names | string | Optional: Filters by a comma-separated list of schema names. | No | |
| limit | integer | Optional: The maximum number of rows to return. | No | 50 |
List key details for all PostgreSQL replication slots (e.g., type, database, active status) and calculates the size of the outstanding WAL that is being prevented from removal by the slot.
Lists each replica's process ID, user name, application name, backend_xmin (standby's xmin horizon reported by hot_standby_feedback), client IP address, connection state, and sync_state, along with lag sizes in bytes for sent_lag (primary to sent), write_lag (sent to written), flush_lag (written to flushed), replay_lag (flushed to replayed), and the overall total_lag (primary to replayed).