Skip to main content
Skip table of contents

PostgreSQL matrix

Delphix Support Policies specifically list Major and Minor release coverage. If a minor release is listed as covered, then all patch releases under that minor release are certified.

Key:

Color

Supported?

Y

Yes

N

No

RHEL/CentOS/SUSE/Ubuntu

Supported OS Version

Supported DBMS Version (Open-source & EDB)

9.4.x (Open-source & EDB)

9.5.x (Open-source & EDB)

9.6.x (Open-source & EDB)

10.x (Open-source & EDB)

11.x (Open-source & EDB)

12.x (Open-source & EDB)

13.x (Open-source & EDB)

14.x (Open-source& EDB)

15.x (Open-source& EDB)

RHEL/CentOS 7.3

Y

Y

Y

Y

Y

Y

N

N

N

RHEL/CentOS 7.4

Y

Y

Y

Y

Y

Y

N

N

N

RHEL/CentOS 7.5

Y

Y

Y

Y

Y

Y

N

N

N

RHEL/CentOS 7.6

Y

Y

Y

Y

Y

Y

N

N

N

RHEL/CentOS 7.7

Y

Y

Y

Y

Y

Y

N

N

N

RHEL/CentOS 7.8

N

N

Y

Y

Y

Y

N

N

N

RHEL 7.9

N

N

Y

Y

Y

Y

Y

Y

N

Centos 7.9

N

N

N

N

N

Y

Y

Y

N

RHEL 8.0

N

N

N

N

N

Y

Y

Y

Y

RHEL 8.1

N

N

N

N

N

Y

Y

Y

Y

RHEL 8.2

N

N

N

N

N

Y

Y

Y

Y

RHEL 8.3

N

N

N

N

N

Y

Y

Y

Y

RHEL 8.4

N

N

N

N

N

Y

Y

Y

Y

RHEL 8.5

N

N

N

N

N

Y

Y

Y

Y

RHEL 8.6

N

N

N

N

N

Y

Y

Y

Y

RHEL 8.7

N

N

N

N

N

Y

Y

Y

Y

RHEL 8.8

N

N

N

N

N

Y

Y

Y

Y

RHEL 8.9

N

N

N

N

N

Y

Y

Y

Y

RHEL 9.0

N

N

N

N

N

N

N

N

Y

SUSE 11

Y

N

N

N

N

N

N

N

N

SUSE 12

Y

Y

Y

Y

Y

N

N

N

N

SUSE 15

N

N

N

N

N

N

Y

N

N

Ubuntu 16.04

N

N

N

Y

N

N

N

N

N

SUSE 15SP3

N

N

N

N

N

N

Y

N

N

where x represents the minor version.

  • All the available PostgreSQL Database minor versions will be supported for the above-mentioned major versions.

  • SUSE 15SP3 is supported on Power 8 hardware.

  • Make sure to install libncurses.5 or libncurses.6 in the host, for supporting RHEL and SUSE. You can refer KBA 5622 for actionable steps.

Cloud vendors

Supported cloud vendors

PostgreSQL 11

PostgreSQL 12

PostgreSQL 13

PostgreSQL 14

Amazon RDS PostgreSQL

Y

Y

Y

Y

Amazon Aurora PostgreSQL

Y

Y

Y

Y

Azure Flexible Server

Y

Y

Y

Y

Only a single DB ingestion feature is supported for the Cloud Vendors ( Amazon RDS/Aurora and Azure Single/Flexible Server) PostgreSQL through the pg_dump/pg_restore method.

Plugin/Delphix Engine compatibility

Plugins should be installed on compatible Delphix Engines per the table below:

The plugin versions from 1.0.1 till 1.3.2 are currently in extended support. Please reach out to Delphix customer support for any queries.

Currently, PostgreSQL Plugin 1.4.1 is not supported on SUSE 12.x.

Delphix Engine Version

Plugin Version

1.4.0

1.4.1

1.4.2

1.4.3

1.4.4

1.5.0

1.5.1

2.0.0

2.1.0

2.1.1

3.0.0

3.1.0

3.2.0

4.0.0

4.1.0

4.1.1

6.0.0.x

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

6.0.1.x

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

6.0.2.x

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

6.0.3.x

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

6.0.4.x

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

6.0.5.x

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

6.0.6.x

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

6.0.7.x

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

6.0.8.x

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

6.0.9.x

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

6.0.10.x

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

6.0.11.x

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

6.0.12.x

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

6.0.13.x

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

6.0.14.x

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

N

6.0.15.x

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

6.0.16.x

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

6.0.17.x

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

7.0.0.x

N

N

N

N

N

N

N

Y

Y

Y

Y

Y

Y

Y

Y

Y

8.0.0.x

N

N

N

N

N

N

N

Y

Y

Y

Y

Y

Y

Y

Y

Y

9.0.0.x

N

N

N

N

N

N

N

Y

Y

Y

Y

Y

Y

Y

Y

Y

10.0.0.x

N

N

N

N

N

N

N

Y

Y

Y

Y

Y

Y

Y

Y

Y

11.0.0.x

N

N

N

N

N

N

N

Y

Y

Y

Y

Y

Y

Y

Y

Y

12.0.0.x

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

13.0.0.x

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

14.0.0.x

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Plugin upgrade path

Path A - New plugin installation for PostgreSQL customers:

  • Upload 4.0.0 Plugin for PostgreSQL 9.4.x, 9.5.x, 9.6.x,10.x, 11.x, 12.x, 13.x,14.x and 15.x customers.

Path B - Existing PostgreSQL customers with different plugin versions:

Your version

Recommended upgrade path to 4.1.1

1.0.1

1.0.2

Upgrade to 1.1.0 and follow the upgrade path below.

1.1.0

Upgrade to 1.2.0 and follow the upgrade path below.

1.2.0

Upgrade to 1.3.0 and follow the upgrade path below.

1.3.0

Upgrade to 1.4.1, 1.4.2, 1.4.3, or 1.4.4 and follow the path below.

1.4.1

1.4.2

1.4.3

Upgrade to 1.5.0 or 1.5.1and follow the path below.

1.5.0

1.5.1

Upgrade to 2.0.0 and follow the upgrade path below.

2.0.0

2.1.0

Upgrade to 3.0.0 and follow the upgrade path below.

3.0.0
3.1.0
3.2.0

 

Upgrade to 4.0.0 and follow the upgrade path below.

4.0.0

4.1.0

Upgrade directly to the latest version 4.1.1.

For PostgreSQL customers with plugin version 1.0.1 or 1.0.2:

Plugin upgrade path: 1.0.1 → 1.1.0 → 1.2.0 → 1.3.0 → 1.4.1/1.4.2/1.4.3/1.4.4 → 1.5.0/1.5.1 → 2.0.0/2.1.0 → 3.0.0 → 3.1.0 → 3.2.0 → 4.0.0→ 4.1.0→ 4.1.1.

Plugin upgrade path 1.0.2 → 1.1.0 → 1.2.0 → 1.3.0 → 1.4.1/1.4.2/1.4.3/1.4.4 → 1.5.0/1.5.1 → 2.0.0/2.1.0 → 3.0.0 → 3.1.0 → 3.2.0 → 4.0.0→ 4.1.0→ 4.1.1.

For PostgreSQL customers with plugin version 1.1.0

Plugin upgrade path: 1.1.0 → 1.2.0 → 1.3.0 → 1.4.1/1.4.2/1.4.3/1.4.4 → 1.5.0/1.5.1 → 2.0.0/2.1.0 → 3.0.0 → 3.1.0 → 3.2.0 → 4.0.0→ 4.1.0→ 4.1.1.

For PostgreSQL customer with plugin version 1.2.0

Plugin upgrade path: 1.2.0 → 1.3.0 → 1.4.1/1.4.2/1.4.3/1.4.4 → 1.5.0/1.5.1 → 2.0.0/2.1.0 → 3.0.0 → 3.1.0 → 3.2.0 → 4.0.0→ 4.1.0→ 4.1.1.

For PostgreSQL customer with plugin version 2.0.0

Plugin upgrade path: 2.0.0/2.1.0 → 3.0.0 → 3.1.0 → 3.2.0 → 4.0.0→ 4.1.0→ 4.1.1.

Upgrading existing objects

In order to upgrade the existing objects with 1.1.0 (i.e 1.0.1 → 1.1.0 or 1.0.2 → 1.1.0), just after the upgrade, it is mandatory to update below two parameters of dSource using the "custom Configuration" option on the UI :

  • Source IP Address

  • Source Port

A critical fault will show up on dSource just after the upgrade. It is because the engine is not able to find the source config from which dSource was created. As we have moved to manual discovery in this release, we need to mark this fault as resolved on the status tab of dSource.

Unsupported PostgreSQL versions and features

  • PostgreSQL versions below 9.4 i.e (9.2, 9.3) are NOT supported by the plugin.

  • It is not possible to access the staging server with PostgreSQL 9.4 and PostgreSQL 9.5 versions.
    The following points describe why staging server is not accessible with PostgreSQL 9.4 and PostgreSQL 9.5 versions.

    1. On staging server, PostgreSQL plugin setups warm standby till version 9.x, which indicates that you cannot access PostgreSQL database on staging instance with PostgreSQL 9.4 and PostgreSQL 9.5 versions or even dSource for READ-ONLY workload. However, in later versions it is possible to trigger READ-ONLY query on dsource.

    2. In PostgreSQL version 9.x, the plugin sets wal_level parameter on staging server PostgreSQL instance to archive. However for PostgreSQL version 10 and later, PostgreSQL plugin sets wal_level parameter on staging server PostgreSQL instance to hot_standby or replica.

  1. Warm Standby/Log Shipping is a HA solution which 'replicates’ a database cluster to an archive or a warm (can be brought up quickly, but not available for querying) standby server. Overhead is very low and it’s easy to set up. This is a simple and appropriate solution if all you care about is continuous backup and short failover times.

  2. Hot Standby/Streaming Replication provides asynchronous binary replication to one or more standbys. Standbys may also become hot standbys meaning they can be queried as a read-only database. This is the fastest type of replication available as WAL data is sent immediately rather than waiting for a whole segment to be produced and shipped. In hot_standby level, the same information is logged as with archive, plus information needed to reconstruct the status of running transactions from the WAL. To enable read-only queries on a standby server, wal_level must be set to ‘hot_standby’ or higher on the primary, and hot_standby must be enabled in the standby.

    Dsource created in PostgreSQL 9.4 & 9.5 version is a warm standby so it is not accessible. wal_level determines how much information is written to the WAL. The default value is minimal, which writes only the information needed to recover from a crash or immediate shutdown. archive adds logging required for WAL archiving; hot_standby further adds information required to run read-only queries on a standby server; and, finally logical adds information necessary to support logical decoding. Each level includes the information logged at all lower levels. This parameter can only be set at server/instance level.

  • There are two features that are not supported by the plugin:

    1. Unlogged Tables: All the tables which are not logged (unlogged) will not be supported by the Plugin.

    2. Point In Time recovery: Currently, the Plugin doesn’t support Point in Time recovery of the PostgreSQL database.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close