PostgreSQL Replication's second chapter understands the transaction log of PostgreSQL (2)

2.2 Xlog and Replication

In this chapter, you have learned that the transaction log for PostgreSQL has made all changes to the database. The transaction log itself is packaged as an easy-to-use 16MB segment.

The idea of using this change set to replicate data is not farfetched. In fact, this is a logical step in the development of each relational (or even non-relational) database system. Other parts of the book, you will see in many ways how the PostgreSQL transaction log can be used, acquired, stored, copied, and analyzed in many different ways.

In most replication systems, the PostgreSQL transaction log is the backbone of the entire architecture (for synchronous replication and asynchronous replication).

PostgreSQL Replication's second chapter understands the transaction log of PostgreSQL (2)