Capabilities for Aurora PostgreSQL
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 13.4, since HVR 5.5.5/2).
- Log-based capture (capture from DBMS logging system) (Aurora PostgreSQL from 2.2 to 13.4).
- Log-based capture of tables without a primary key (Aurora PostgreSQL from 2.2 to 13.4).
- Access to logs using SQL interface (Aurora PostgreSQL from 2.2 to 13.4).
- Log-based capture of tables with LOB column (Aurora PostgreSQL from 2.2 to 13.4).
- Log-based capture of truncate table statements (Aurora PostgreSQL from version 11, since HVR 5.7.5/43).
- Multiple log-based capture jobs can capture from same database (Aurora PostgreSQL from 2.2 to 13.4).
- Log-based capture checkpointing (action Capture /CheckpointingFrequency) (Aurora PostgreSQL from 2.2 to 13.4).
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/RRN column (ColumnProperties /CaptureFromRowId).
- Rewind log-based capture to specific time (Hvrinit option -i).
- Online refresh using accurate LSN/SCN.
- Populates column hvr_cap_user for use in ColumnProperties {hvr_cap_user} substitutions.
- 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 13.4, since HVR 5.3.1/25).
- Integrate with /Burst (Aurora PostgreSQL from 1.0 to 13.4).
- Integrate with /BurstCommitFrequency (Aurora PostgreSQL from 1.0 to 13.4).
- Continuous integration (Integrate without /Burst) (Aurora PostgreSQL from 1.0 to 13.4).
- Action TableProperties with /DuplicateRows for continuous integration (Aurora PostgreSQL from 1.0 to 13.4).
- Continuous Integrate with /OnErrorSaveFailed (without /Burst) (Aurora PostgreSQL from 1.0 to 13.4).
- Action Transform /SoftDelete (Aurora PostgreSQL from 1.0 to 13.4).
- Creation and update of HVR state tables (Aurora PostgreSQL from 1.0 to 13.4).
HVR does not support the following capabilities on Aurora PostgreSQL:
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 13.4, state table needs to be created before replication starts).
- CollisionDetect with /TimestampColumn (Aurora PostgreSQL from 1.0 to 13.4).
HVR does not support the following capabilities on Aurora PostgreSQL:
- CollisionDetect with Log-based Capture (without /TimestampColumn).
Refresh and Compare
HVR supports the following capabilities on Aurora PostgreSQL:
- Hvrrefresh or Hvrcompare from source location (Aurora PostgreSQL from 1.0 to 13.4, since HVR 5.3.1/25).
- Hvrrefresh into target location (Aurora PostgreSQL from 1.0 to 13.4).
- Row-wise Hvrrefresh into target location (option -g) (Aurora PostgreSQL from 1.0 to 13.4).
- 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 13.4).
Other Capabilities
HVR supports the following capabilities on Aurora PostgreSQL:
- Call database procedure dbproc during replication jobs (action AgentPlugin /DbProc) (Aurora PostgreSQL from 10.18 to 13.4, 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 13.4).
- Treat DBMS table names and columns as case sensitive if configured (action LocationProperties /CaseSensitiveNames defined) (Aurora PostgreSQL from 1.0 to 13.4, since HVR 5.3.1/25).
- Always treat DBMS table names and column names as case sensitive, even if not configured (action LocationProperties /CaseSensitiveNames not defined) (Aurora PostgreSQL from 1.0 to 13.4).
- Always treat DBMS schema names case sensitive (Aurora PostgreSQL from 1.0 to 13.4).
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'.