Help Center/ Data Replication Service/ User Guide (Kuala Lumpur Region)/ FAQs/ Real-Time Synchronization/ What Are Impacts of Setting the Replication Attribute of Tables to full for Incremental Synchronization from PostgreSQL or GaussDB?
Updated on 2025-08-07 GMT+08:00
View PDF
Share

What Are Impacts of Setting the Replication Attribute of Tables to full for Incremental Synchronization from PostgreSQL or GaussDB?

When PostgreSQL or GaussDB is used as the source database for incremental synchronization, the replication attribute of some tables must be set to full to meet data synchronization requirements.

Setting the replication attribute of a table to full has the following impacts on the source database:

  • Extra storage space: As all column data in a database needs to be stored, for UPDATE operations, the database may need to store extra row version data, which increases the storage space usage.

  • Increased size of transaction logs (WALs): If REPLICA IDENTITY is set to FULL, more data is recorded in transaction logs because complete row data needs to be recorded for each UPDATE or DELETE operation. This may cause transaction logs to grow faster, which may require more frequent log rotation.

  • Increased transaction processing time: As more data needs to be recorded, the time for processing UPDATE and DELETE operations may increase, which may affect the transaction response time and throughput. Also, the impact may depend on the database performance and data model of a table.