Capture Latency Increases with CaptureCondition on the Source

Issue

Capture latency increases even though the source database, network, and source application all appear to function normally. In this scenario, the added latency comes from a Restrict action's CaptureCondition parameter defined at the source location.

Environment

• HVR 5
• Source: PostgreSQL 14

Resolution

To resolve this issue, in the Restrict action, replace the CaptureCondition parameter on the source location with the IntegrateCondition parameter on the target. This eliminates per-transaction condition evaluation during Capture, reducing the likelihood of increased latency.

Cause

This issue occurs when a CaptureCondition parameter is defined on the source location. When this happens, Capture evaluates the condition for every transaction read from the source database’s transaction log, even if the transaction is uncommitted or doesn't affect a replicated object. This processing increases capture latency.