Capabilities for Aurora PostgreSQL

Last updated on Jan 05, 2021

Contents

This section lists the Capabilities of HVR when using 'Aurora PostgreSQL'. For more information about the pre-requisites, access privileges, and other configuration requirements, see Requirements for PostgreSQL.

Capture

HVR supports the following capabilities on Aurora PostgreSQL:

  • Capture changes from location (Aurora PostgreSQL from 1.0 to 3.2, since HVR 5.5.5/2).
  • Log-based capture (capture from DBMS logging system) (Aurora PostgreSQL from 2.2 to 3.2).
  • Log-based capture of tables without a primary key (Aurora PostgreSQL from 2.2 to 3.2).
  • Access to logs using SQL interface (Aurora PostgreSQL from 2.2 to 3.2).
  • Log-based capture of tables with LOB column (Aurora PostgreSQL from 2.2 to 3.2).
  • Rewind log-based capture to specific time (Hvrinit option -i) (Aurora PostgreSQL from 2.2 to 3.2).
  • Rewind log-based capture to the beginning of currently active oldest transaction (Aurora PostgreSQL from 2.2 to 3.2).
  • Multiple log-based capture jobs can capture from same database (Aurora PostgreSQL from 2.2 to 3.2).
  • Log-based capture checkpointing (action Capture /CheckpointingFrequency) (Aurora PostgreSQL from 2.2 to 3.2).

HVR does not support the following capabilities on Aurora PostgreSQL:

  • Capture from Archive log files only.
  • Log-based capture of DDL statements using action AdaptDDL.
  • Direct access to logs on a file system.
  • Log-based capture from hidden rowid column (ColumnProperties /CaptureFromRowId).
  • Rewind log-based capture to the beginning of currently active oldest transaction for a specific list of tables.
  • Online refresh using accurate LSN/SCN.
  • Populates column hvr_cap_user for use in ColumnProperties {hvr_cap_user} substitutions.
  • Log-based capture of truncate table statements.
  • Capture from tables with basic compression.
  • Hvrlogrelease to preserve journal/archives.
  • Read archives from an alternative directory (Capture /ArchiveLogPath).
  • Trigger-based capture (action Capture /TriggerBased).

Hub Database

HVR supports Hub database on Aurora PostgreSQL.

Integrate

HVR supports the following capabilities on Aurora PostgreSQL:

  • Integrate changes into location (Aurora PostgreSQL from 1.0 to 3.2, since HVR 5.3.1/25).
  • Integrate with /Burst (Aurora PostgreSQL from 1.0 to 3.2).
  • Integrate with /BurstCommitFrequency (Aurora PostgreSQL from 1.0 to 3.2).
  • Continuous integration (Integrate without /Burst) (Aurora PostgreSQL from 1.0 to 3.2).
  • Action TableProperties with /DuplicateRows for continuous integration (Aurora PostgreSQL from 1.0 to 3.2).
  • Continuous Integrate with /OnErrorSaveFailed (without /Burst) (Aurora PostgreSQL from 1.0 to 3.2).
  • Action Transform /SoftDelete (Aurora PostgreSQL from 1.0 to 3.2).
  • Creation and update of HVR state tables (Aurora PostgreSQL from 1.0 to 3.2).

HVR does not support the following capabilities on Aurora PostgreSQL:

  • Disable/enable database triggers during Integrate (/NoTriggerFiring).
  • Integrate with /DbProc.

Bi-directional Replication

HVR supports the following capabilities on Aurora PostgreSQL:

  • Detection of changes made by HVR in a bidirectional channel to prevent loop-back (Aurora PostgreSQL from 1.0 to 3.2, since HVR 5.5.5/2).
  • CollisionDetect with /TimestampColumn (Aurora PostgreSQL from 1.0 to 3.2, since HVR 5.5.5/2).

HVR does not support the following capabilities on Aurora PostgreSQL:

Refresh and Compare

HVR supports the following capabilities on Aurora PostgreSQL:

  • Hvrrefresh or Hvrcompare from source location (Aurora PostgreSQL from 1.0 to 3.2, since HVR 5.3.1/25).
  • Hvrrefresh into target location (Aurora PostgreSQL from 1.0 to 3.2).
  • Row-wise Hvrrefresh into target location (option -g) (Aurora PostgreSQL from 1.0 to 3.2).
  • Select data from each table from same consistent moment in time using a single transaction (and session) with 'serializable' SQL isolation level (Hvrrefresh option -Mserializable) (Aurora PostgreSQL from 1.0 to 3.2).

Other Capabilities

HVR supports the following capabilities on Aurora PostgreSQL:

  • Call database procedure dbproc during replication jobs (action AgentPlugin /DbProc) (Aurora PostgreSQL from 3.0 to 3.2, since HVR 5.3.1/25).
  • International table and column names where DBMS is not configured with UTF-8 encoding (Aurora PostgreSQL from 1.0 to 3.2).
  • Treat DBMS table names and columns case sensitive (action LocationProperties /CaseSensitiveNames) (Aurora PostgreSQL from 1.0 to 3.2, since HVR 5.3.1/25).
  • Always treat DBMS table names and column names case sensitive (Aurora PostgreSQL from 1.0 to 3.2).
  • Always treat DBMS schema names case sensitive (Aurora PostgreSQL from 1.0 to 3.2).

HVR does not support the following capabilities on Aurora PostgreSQL:

  • Use distribution key for parallelizing changes within a table (ColumnProperties /DistributionKey).
  • Distinguish and support capture from 'materialized views'.