This page provides information about working with read replicas. For information about how to configure a read replica, see Creating Read Replicas.
Read replicas are Cloud SQL instances that replicate from a Cloud SQL master instance.
- Read replicas neither provide high availability nor offer it; a master instance cannot fail over to a read replica, and read replicas are unable to fail over in any way during an outage.
- Read replicas do not support the maintenance window setting; they can experience a disruptive upgrade at any time.
- If the master instance fails over, read replicas do not change zones. Until the master fails back to its original zone, read replicas are in a different zone than the master instance.
- Creating a read replica does not impact the performance or availability of the master instance.
- You can create multiple read replicas for a single master instance. Cloud SQL does not provide load balancing between replicas.
- The settings of the master instance are propagated to the replica, including the password for the postgres user and changes to the user table.
- Read replicas can have more CPUs and memory than the master instance, but they cannot have less.
- Read replicas must be in the same region as the master instance.
- You cannot make changes to the user table on the replica. All user changes must be done on the master instance.
- You cannot configure backups on the replica.
- You cannot restore the master of a replica while the replica exists. Before restoring an instance from a backup, you must promote or delete all of its replicas.
- Before you can delete a master instance, you must promote all of its read replicas to stand-alone instances or delete the read replicas.
- You cannot create a replica of a replica.
- A read replica is charged at the same rate as a standard Cloud SQL instance. There is no charge for the data replication.