managing-database-replication

Master-slave replication configures a primary database to automatically sync changes to one or more replica servers. This Skill automates the setup process by prompting for connection details, generating the necessary replication commands for your chosen database, and establishing the replication stream to enable read scaling and failover capability.

Physical replication copies the database's underlying storage blocks, offering lower overhead and faster recovery. Logical replication copies individual row changes, allowing selective replication and compatibility across PostgreSQL versions. This Skill supports both modes so you can choose based on your consistency and operational requirements.

Automatic failover detects when the master database fails and promotes a replica to become the new master, redirecting client connections to maintain service. This Skill configures the failover mechanism and monitoring thresholds, so your database cluster continues operating without manual intervention during outages.

Replication lag monitoring tracks how far behind replicas are from the master. This Skill implements lag tracking and supports alert triggers when lag exceeds your defined thresholds, helping you catch performance issues before they impact read consistency or failover readiness.

Yes. The Skill guides you through configuration by collecting your existing master and replica connection details, replication parameters, and failover preferences. It then generates and executes commands to establish replication on your current PostgreSQL or MySQL instances without requiring a full database migration.

You need at least two running PostgreSQL or MySQL instances, network connectivity between them, appropriate user privileges for replication operations, and knowledge of connection details like host, port, and credentials. The Skill prompts for this information during configuration.