SharePlex supports the following functionality for PostgreSQL Database as a Service as source:
Cloud database service: Logical replication on the below platforms
AWS: Amazon RDS for PostgreSQL, Amazon Aurora
Azure: PostgreSQL on Flexi Server
Note: SharePlex supports logical replication with the pgoutput plugin only.
SharePlex supports data replication for the PostgreSQL Database as a Service according to the below source target combinations:
Oracle 21c: Support for Oracle 21c is included in this release.
FIPS Compliant SharePlex: SharePlex installations can now be run on FIPS-enabled servers only on the Linux platform.
SharePlex supports physical and logical replication with PostgreSQL on-premise database.
Users can now configure the Post process to log information about conflict resolution operations using the SharePlex prepared routines for the PostgreSQL database.
SharePlex now supports the BOOLEAN, TIME, BYTEA, and TIME WITH TIMEZONE data types for PostgreSQL as a source.
Users can now replicate data from PostgreSQL to PostgreSQL when the database name has hyphen, dot, and plus (-, ., +) characters.
SharePlex now supports High Availability with CrunchyData for PostgreSQL on-premises database with physical and logical replication.
SharePlex now supports Kafka partitioning based on 'messagekey' for Oracle as a source.
SharePlex supports the Show Last Posted feature for the PostgreSQL database.
SharePlex now supports replication from PostgreSQL Timestamp to Oracle/PostgreSQL Date data types.
Users can now activate configuration with LSN using the user-provided LSN for PostgreSQL as a source.
Limitation: This command option is supported only for physical replication.
SharePlex supports the trigger scripts for replicating data from PostgreSQL to PostgreSQL database.
SharePlex supports the configuration scripts for replicating data from PostgreSQL to supported target databases.
Users no longer need to follow case-sensitivity for column names in the config file while replicating data from PostgreSQL to Oracle.
SharePlex now supports long table and column names with more than 30 characters for Oracle as a source.
Limitation: In Oracle to other RDBMS (PostgreSQL, SQL Server, and MySQL) target replication, if a table being replicated has a column name longer than 30 characters and there are uncommitted inserts followed by update operations within a given transaction, the open Poster process will fail to replicate the data and display an error. This occurs because the supplemental key data is not available in Oracle's REDO log, resulting in the Poster process stopping.
Support for OpenSSL 3.0.8.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center