Configuration Parameter and Table Setting Requirements v6.2
Depending upon the multi-master replication system environment, certain configuration settings may be required in order for the conflict resolution process to operate properly.
The following are required only for the log-based method. These do not apply to the trigger-based method.
track_commit_timestamp
. Any Postgres 10 and later database server containing a primary node must have itstrack_commit_timestamp
configuration parameter enabled. Thetrack_commit_timestamp
parameter is located in thepostgresql.conf
file. Iftrack_commit_timestamp
is not enabled, thenupdate/update
conflicts are not automatically resolved such as by using the earliest timestamp of the conflicting transactions. As a result, these conflicting transactions are left in a pending state. See Automatic Conflict Resolution Example for an example of how update/update conflicts are automatically resolved.REPLICA IDENTITY FULL.
Ifupdate/update conflicts
are expected to occur on a given publication table, then theREPLICA IDENTITY
setting for the table must be set to FULL on every primary node. The case where update transactions occur on separate primary nodes, but updating different columns in the same row, is not considered an update/update conflict. However, ifREPLICA IDENTITY
is not set toFULL
, then this case will be recorded as anupdate/update conflict
.
The REPLICA IDENTITY
option is set to FULL
using the ALTER TABLE
command as shown by the following:
The following is an example of the ALTER TABLE
command:
The REPLICA IDENTITY
setting can be displayed by the PSQL utility using the \d+
command:
Note
In addition to conflict resolution requirements, the REPLICA IDENTITY FULL
setting may be required on publication tables for other reasons in xDB Replication Server. See Table Settings and Restrictions for Table Filters for additional requirements.