.png){kind=logo}
PostgreSQL 3.1.0 Release Notes
- 28 Feb 2023
- 3 Minutes to read
-
Print
-
DarkLight
-
PDF
PostgreSQL 3.1.0 Release Notes
- Updated on 28 Feb 2023
- 3 Minutes to read
-
Print
-
DarkLight
-
PDF
New Features
Source Sizing Implementation on PostgreSQL Plugin
This feature enables you to check the size of PostgreSQL cluster or database being virtualized from the Delphix Engine. The calculation of the dataset size is based on the ingestion method used. For staging pull methods, if the whole cluster is ingested then the size of the cluster will be calculated or else the size of the ingested single database will be calculated. Source sizing cannot be implemented when staging push method is used.
This feature requires the plugin to run SQL queries on the datasets. If the plugin cannot login to the dataset for any reason, then source sizing cannot be implemented.
For more details about this feature, see Source Sizing Implementation for dSource and Source Sizing Implementation for VDB.
If you are using privilege elevation and upgrading to PostgreSQL 3.1.0 version, then you will have to change the sudoers entry. For more details see, Prerequisites for Privilege Elevation using DLPX_DB_EXEC Script.
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? |
|---|---|
| Yes |
 | No |
RHEL/CentOS/SUSE/Ubuntu
| Supported OS Version | 9.4.x | 9.5.x | 9.6.x | 10.x | 11.x | 12.x (Open-source & EDB) | 13.x (Open-source & EDB) | 14.x (Open-source & EDB) | EnterpriseDB (Open-source & EDB) |
|---|---|---|---|---|---|---|---|---|---|
| Supported DBMS Version | |||||||||
| RHEL/CentOS 7.3 |
|
|
|
|
|
| | | |
| RHEL/CentOS 7.4 |
|
|
|
|
|
| | | |
| RHEL/CentOS 7.5 |
|
|
|
|
|
| | | |
| RHEL/CentOS 7.6 |
|
|
|
|
|
| | | |
| RHEL/CentOS 7.7 |
|
|
|
|
|
| | | |
| RHEL/CentOS 7.8 | | |
| | |
| | | |
| RHEL 7.9 | | |
|
| |
|
| | |
| RHEL 8.3 | | | | | |
|
|  | |
| RHEL 8.6 | | | | | | | | | |
| SUSE 11 |
| | | | | | | | |
| SUSE 12 |
|
|
|
|
| | | | |
| SUSE 15 | | | | | | |
| | |
| Ubuntu 16.04 |
|
|
|
|
|
|
| |
|
| SUSE 15SP3 |
|
|
|
|
|
|
| |
|
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 |
|---|---|---|---|
| Amazon RDS PostgreSQL |
|
|
|
| Amazon Aurora PostgreSQL |
|
|
|
For this release, only a single DB ingestion feature is supported for the Amazon RDS/Aurora 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.
| Plugin Version | ||||||||||||
Delphix Engine 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 6.0.0.x |
|
|
|
|
|
|
| | | | | |
| 6.0.1.x |
|
|
|
|
|
|
| | | | | |
| 6.0.2.x |
|
|
|
|
|
|
| | | | | |
| 6.0.3.x |
|
|
|
|
|
|
| | | | | |
| 6.0.4.x |
|
|
|
|
|
|
| | | | | |
| 6.0.5.x |
|
|
|
|
|
|
| | | | | |
| 6.0.6.x |
|
|
|
|
|
|
| | | | | |
| 6.0.7.x |
|
|
|
|
|
|
| | | | | |
| 6.0.8.x |
|
|
|
|
|
|
| | | | | |
| 6.0.9.x |
|
|
|
|
|
|
| | | | | |
| 6.0.10.x |
|
|
|
|
|
|
| | | | | |
| 6.0.11.x |
|
|
|
|
|
|
| | | | | |
| 6.0.12.x |
|
|
|
|
|
|
| | | | | |
| 6.0.13.x |
|
|
|
|
|
|
| | | | | |
| 6.0.14.x |
|
|
|
|
|
|
|
|
|
| | |
| 6.0.15.x |
|
|
|
|
|
|
|
|
|
|
| |
| 6.0.16.x |
|
|
|
|
|
|
|
|
|
|
|
|
| 6.0.17.x |
|
|
|
|
|
|
|
|
|
|
|
|
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.
- Broadly there are two features that are not supported by the plugin:
- Unlogged Tables: All the tables which are not logged (unlogged) will not be supported by the Plugin.
- Point In Time recovery: Currently, the Plugin doesn’t support Point in Time recovery of the PostgreSQL database.
Plugin Upgrade Path
Path A - New Plugin installation for PostgreSQL customers:
- Upload 3.1.0 Plugin for PostgreSQL 9.4.x, 9.5.x, 9.6.x,10.x, 11.x, 12.x, and 13.x customers
Path B - Existing PostgreSQL customers with different Plugin versions:
Your Version | Recommended Upgrade Path to 3.1.0 |
|---|---|
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 directly to 1.5.0 or the latest version 1.5.1. |
1.5.0 1.5.1 | Upgrade directly to 2.0.0 and follow the upgrade path below. |
2.0.0 2.1.0 | Upgrade directly to 3.0.0. |
| 3.0.0 | Upgrade directly to the latest version 3.1.0. |
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
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
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
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
For PostgreSQL customer with Plugin version 2.0.0
Plugin upgrade path: 2.0.0/2.1.0 → 3.0.0→ 3.1.0
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.
Fixed Issues
PostgreSQL version 3.1.0 contains the following bug fixes and enhancements:
| Ticket Number | Summary |
|---|---|
| POST-596 | New mechanism of creating files to remove wildcard entry for `echo` in sudoers file. |
| POST-611 | Ubuntu Certification >> Linking is failing when pg_hba.conf and pg_ident.conf files are not at data directory |
| POST-642 | dSource Single DB Ingestion >> User should not be allowed to change database name parameter, unless it's a RESYNC operation |
| POST-668 | Staging Push >> Failure to provision a VDB using privilege elevation from Staging Push snapshot with provisioning allowed |
Was this article helpful?