1.1 What’s New

Table of Contents Previous Next


1 Introduction : 1.1 What’s New

The DDL change replication feature now supports acceptance of ALTER TABLE statements by direct entry into the Alter Publication Table dialog box by copying and pasting the statement text from another source, or by typing the statements directly into the dialog box. Previously, the statements must be provided by means of a saved text file. For more information, see Section 7.8.
Publication tables containing Postgres built-in range types int4range, int8range, numrange, tsrange, tstzrange, or daterange can now be included in an SMR or MMR system as long as all of the participating database servers are version 9.2 or later. For more information, see Section 2.4.3.
Publication tables containing the Postgres line geometric data type can now be replicated with either the trigger-based method or the log-based method of synchronization replication. Previously, only the log-based method could be used.
The output returned and displayed in the xDB Replication Console from a snapshot replication has now been eliminated by default in order to prevent a delay in response particularly in a network address translation (NAT) environment. For information on controlling this verbose output displayed by the xDB Replication Console, see sections 5.4.1, 6.3, and 6.5.1. In a similar manner, the xDB Replication Server CLI verboseSnapshotOutput parameter can be used to control the snapshot replication output from the addpubdb command (see Section 8.3.7), the dosnapshot command (see Section 8.3.40), and the dommrsnapshot command (see Section 8.3.41).
Shadow table history cleanup can now be specified for a specific set of master nodes using the xDB Replication Server CLI mmrdbid parameter of the cleanshadowhistforpub command. Previously, the cleanshadowhistforpub command affected all master nodes by default. For more information, see Section 8.3.49.
xDB Replication Server product registration can now be done with the xDB Replication Server CLI registerkey command. This eliminates the necessity of using the xDB Replication Console for this purpose. For more information, see Section 8.3.4.
The custom conflict handling function name can now be specified with the xDB Replication Server CLI customhandlername parameter of the updateconfresolutionstrategy command. For more information, see Section 8.3.24.
The publication server configuration option walTxSetCreationInterval has been added to enable you to control the time interval between transaction sets when using the newly supported, log-based method of synchronization replication. This option helps you to improve synchronization performance based upon the transaction processing rate impact on the target publication database. For information, see Section 10.4.1.14.
The publication server configuration option dataSyncThreadCount has been added to control parallel mode usage of a multi-CPUs/core system architecture for synchronization replication to target slave databases or master nodes. For more information, see Section 5.8.2.2.
The publication server configuration option walStreamQueueLimit has been added to limit the number of WAL entries in the queue pending transaction processing for the log-based method of synchronization replication. Once the transactions have been popped out of the queue for processing providing additional space, the WAL stream receiver releases its block on the queue. For more information, see Section 10.4.1.14.
The publication server configuration option pendingTxSetThreshold has been added for the log-based method of synchronization replication to put extraction of data from the WAL stream on hold when the threshold limit for the number of pending transaction sets has been reached. This prevents the situation where data is continuously pushed from the WAL stream channel, but is not being processed or applied resulting in a potential out of memory problem. For more information, see Section 10.4.1.14.
The publication server configuration option jdbc.pool.validationQueryTimeout has been added to control the timeout interval before connection validation queries to the Apache Database Connection Pooling (DBCP) framework fail. For more information, see Section 10.4.1.15.

1 Introduction : 1.1 What’s New

Table of Contents Previous Next