The replication feature synchronizes the master PostgreSQL server to a standby PostgreSQL server by replicating logs from the backup of the master server to a synced standby server. The replication operation continuously applies log files from the master database backups since the last sync point.
Note
Backup and restore operations for this feature can be performed from PostgreSQL and EnterpriseDB version 9.2 to version 11.
The replication feature performs the following procedures:
-
Initiates the replication automatically after a backup is completed on the master server.
-
Minimizes the impact on production systems CPU and I/O by using the backup data for replications. This method avoids the need to read the master server again for replication.
-
Copies the backup data to remote disaster recovery (DR) sites with deduplication to minimize the wide area network (WAN) traffic. A replication operation then runs at the DR site.
-
Supports the destination database sync in standby mode so that users can schedule workloads on the destination server.
-
Initiates replication after the auxiliary copy completes, when you use a copy precedence for replication operation.
You can use a replication schedule to initiate replication automatically after the backup operation completes on the master server. If no new backup operations have run since the last replication, then the scheduled replication operation does not run.
Use the following backup types to replicate PostgreSQL databases:
-
Traditional backups
-
Auxiliary copies