Help Center/ TaurusDB_TaurusDB for PostgreSQL/ User Guide/ Read Replicas/ Introduction to Read Replicas
Updated on 2026-01-15 GMT+08:00
View PDF
Share

Introduction to Read Replicas

Introduction

TaurusDB for PostgreSQL supports read replicas.

In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and workloads may be affected. To offload read pressure on the primary DB instance, you can create one or more read replicas in the same region as the primary instance. These read replicas can process a large number of read requests and increase application throughput. You need to separately configure connection addresses of the primary DB instance and each read replica on your applications so that all read requests can be sent to read replicas and write requests to the primary DB instance.

A read replica uses a single-node architecture (without a standby node). TaurusDB for PostgreSQL automatically synchronizes changes made on the primary DB instance to all associated read replicas using the PostgreSQL replication. If there is a high network latency on the primary instance, data synchronization to read replicas is affected. Read replicas and the primary DB instance must be in the same region but can be in different AZs.

Billing Standards

Read replicas are billed on a pay-per-use basis.

Functions

  • The specifications of a read replica must be at least equal to those of the primary DB instance to prevent long delay and high load.
  • Pay-per-use billing is supported. You only pay for what you use.
  • You do not need to maintain separate database accounts or databases. They are synchronized from the primary DB instance.
  • Read replicas do not support automated backups or manual backups.
  • Read replicas do not support restoration from backups to new, existing, or original read replicas.
  • Data cannot be migrated to read replicas.
  • Read replicas do not support database creation or deletion.
  • Read replicas do not support database account creation.

Constraints

  • Read replicas cannot be purchased separately. You can purchase them only for your created DB instance.
  • A maximum of five read replicas can be created for a DB instance.
  • The specifications of a read replica must be at least equal to the specifications of the DB instance.

Creating and Managing a Read Replica

Parent Topic: Read Replicas