-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating

Mastering PostgreSQL 15
By :

So far, asynchronous replication has been covered in reasonable detail. However, asynchronous replication means that a commit on a slave is allowed to happen after the commit on a master. If the master crashes, data that has not made it to the slave might yet be lost even if replication is occurring.
Synchronous replication is here to solve the problem – if PostgreSQL replicates synchronously, a commit has to be flushed to disk by at least one replica to go through on the master. Therefore, synchronous replication basically reduces the odds of data loss substantially.
In PostgreSQL, configuring synchronous replication is easy. Only two things have to be done (in any order):
synchronous_standby_names
setting in the postgresql.conf
file on the masterapplication_name
setting to the primary_conninfo
parameter in the config
file in the replicaLet’s get started with the postgresql.conf
file on...