Skip to main content
Skip table of contents

Fixed issues (PostgreSQL)

Release 4.2.3

Key

Summary

POST-442

Postgres: snapsync with resync says it will block share but does not

POST-963

Poor error when dSource fails to Enable due to a failure during DB_SYNC after adding new dSource

POST-971

Postgresql plugin fails to provision on hosts without locale en_US.UTF-8 installed

POST-1003

min_wal_size should be copied from source

POST-1094

Tablespace handling isn't working correctly for VDBs provisioned from single db ingestion dSource snapshot

POST-1082

Revert POST-1027 change for graceful restore

POST-1100

Restrict upgrade from LUA to 4.2.3 version of vSDK directly

Release 4.2.2

Key

Summary

POST-1000

Staging push error "Not able to find database files inside it" confuses users

POST-1025

The PG dSource cluster should not be stopped to run a snapsync operation in any case

POST-1040

Pg_dumpall command should use single database parameter 

Release 4.2.1

Key

Summary

POST-1027

PostgreSQL SnapSync fails to restore certain tables but succeeds without warning users

POST-1013

Postgresql VDB is not closing open connections during refresh / rollback 

POST-1034

Source sizing is failing in plugin with internal error

Release 4.2.0

There are no fixed issues in this release.

Release 4.1.1

Key

Summary

POST-690

Incorrect error: The mount path has been changed from the UI

POST-936

def locate_files & def __find_repo_using_env_variable are not able to suppress the warning "Permission denied"

Release 4.1.0

Key

Summary

POST-720

Postgres staging and target database should use the same local as the source database

POST-85

The Plugin post-snapshot workflow breaking for non-english locales

Release 4.0.0

There are no fixed issues in this release.

Release 3.2.0

Ticket number

Summary

POST-293

Compressed backup and backup timestamp

POST-470

Pg_vSDK >> Plugin should add a parameter to control debug log ON/OFF in `dlpx_pg_logrotate.conf`

POST-497

Ingestion from backup should be more efficient

POST-699

Removing source sizing for VDB

Release 3.1.0

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

Release 3.0.0

Ticket number

Summary

POST-537

postgresql.auto.conf and recovery.signal config files needs to be handled in VDB creation

POST-546

`logging_collector` should be enabled for the dSource

POST-563

SP >> Snapshot operation is failing if the port value is quoted with the strings in config file

POST-565

PG 2.1.1 >> Variable value is missing in error

POST-566

Time difference issue between Delphix Engine and Staging Environment Host

POST-571

Environment variables between low-privileged user & high-privileged user are not translated

Release 2.1.1

Ticket number

Summary

POST-555

Logging of large content is failing at staging/target side

POST-562

Echo command in .bash_profile of the user blocks several Plugin operations

Release 2.1.0

Ticket number

Summary

POST-494

Using dlpx_db_exec for privilege elevation

POST-511

`max_connections` parameter on staging should be set according to the source

POST-518

`netstat` utility is not available in SuSE 15

Release 2.0.0

PostgreSQL version 2.0.0 contains the following bug fixes and enhancements:

Ticket number

Summary

POST-300

pg_basebackup failure not captured

POST-303

Default value for PostgreSQL Mount Path is wrong

POST-306

Delphix GUI allows PostgreSQL VDB port to be changed while the VDB is running

POST-422

Snapshots created for dSource despite failure to start staging database

POST-428

Instance failure reason not captured

POST-431

Unable to provision PostgreSQL VDB with parameters that use the strftime specification formatting

POST-441

Postgres dsource creation with existing backup fails due to missing wal file

Release 1.5.1

Ticket number

Summary

POST-418

Replication monitoring - Lua plugin

Release 1.5.0

Ticket number

Summary

POST-202

If the port is not present in postgresql.conf on the source, it's not provided in staging and VDBs

POST-283

Security enhancement - Plugin overrides listen_addresses parameter in posgresql.conf to "localhost" on staging & target server

POST-292

dSource configuration parameters don't accept empty values

POST-295

The staging server is created using a copy of the production parameters file

POST-297

Postgres Plugin Should check if the toolkit directory is accessible by the OS user

POST-298

primary_conninfo' parameter is not getting commented out in vdb flow

POST-302

Allow users to set empty values for a parameter in a configuration file

POST-312

delphix_postgres_debug.log is too large to manage

POST-316

Propagation of Hotfix 1112 code changes to plugin 1.5.0 release

Release 1.4.4

Key

Summary

POST-291

Error Handling for Authentication Failure in pg_basebackup command

Release 1.4.3

Key

Summary

POST-284

The plugin doesn't check if the staging Postgres database is in a stable state or not

Release 1.4.2

Key

Summary

POST-274

`data_directory` parameter in the postgresql.conf file is causing failure in dSource and VDB flow

POST-275

Linking Fails if the parameter which needs to be configured is commented through multiple `#`

POST-276

Linking Fails if the mandatory parameter required to setup replication is commented in config file

Release 1.4.1

Key

Summary

POST-269

Postgres DB_SYNC fails - ESCL-3179

POST-270

Plugin should handle postgresql.auto.conf entries during dsource creation

Release 1.4.0

There are no fixed issues in this release.

JavaScript errors detected

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

If this problem persists, please contact our support.