Release Notes

Release Notes

Updated: October 23, 2019

Pivotal Greenplum Backup and Restore utilities are released separately from Pivotal Greenplum Database, and are updated independently of the core server.

Version 1.15.0-1

Pivotal Greenplum Backup and Restore version 1.15.0-1 is a minor release.

Platform Support

Pivotal Greenplum Backup and Restore is compatible with these Greenplum Database versions:

  • Pivotal Greenplum Database 4.3.22 and later
  • Pivotal Greenplum Database 5.5.0 and later
  • Pivotal Greenplum Database 6.0.0 and later

Software Component Versions

This release includes the following utilities:

See Known Issues for a list of issues known to exist in this release.

See Release Numbering Conventions for a description of the Pivotal Greenplum Backup and Restore release numbering scheme.

gpbackup v1.15.0

New Features
  • When the --verbose option is supplied to the gpbackup command, the gpbackup command line is written to the backup log.

Changed Features

  • Optimized a catalog metadata query that retrieves column definitions.
  • Optimized a catalog metadata query that retrieves composite types.
  • Optimized a catalog metadata query that retrieves and quotes rolenames.
  • Optimized how ACCESS SHARE locks are acquired.
  • Optimzied metadata queries for partition details and template definitions by combining into a single query.
  • Optimized metadata queries for tablespace names and storage options by combining into a single query.

Resolved Issues

  • [168548176] When using gpbackup to back up a Greenplum Database 5.7.1 or earlier 5.x release with resource groups enabled, gpbackup returns a column not found error for t6.value AS memoryauditor. This issue has been fixed.
  • [168741911] Improved messages written to the gpbackup log file and fixed typos.
  • [29631] On Greenplum Database 4.3 systems, the gpbackup utility sets the enable_mergejoins server configuration utility to off for the gpbackup session. This resolves any catalog queries that may have failed when the enable_mergejoin parameter was set to on.
  • [30162] When gpbackup receives a termination signal (Ctrl-C, for example) after it has acquired locks, the operating system terminates the gpbackup process, but gpbackup does not clean up processes in the database system tables. This has been fixed.

gpbackup_helper v1.15.0

No changes since the previous release.

gprestore v1.15.0

New Features

  • When restoring a backup set from Greenplum Database 4.3.x or 5.x to Greenplum Database 6.x, gprestore sets the gp_use_legacy_hashops server configuration parameter on so that the table data will be correctly distributed with the legacy hash operators. To use the new jump consistent hash algorithms in Greenplum Database 6, after the backup is restored, set the gp_use_legacy_hashops off and redistribute the tables.
  • When the --verbose option is supplied to the gprestore command, the gprestore command line is written to the restore log.

Resolved Issue

  • [30177] When running gprestore with the --jobs option, messages on stdout and in the log file miscount the number of tables processed, and report an incorrect total number of tables when the restore has completed. This issue has been fixed.
  • [169052763] When restoring only some tables and the statistics for those tables using gprestore with a table filter option and the --with-stats option, gprestore attempted to restore all the table statistics from the backup, not just the statistics for the tables being restored. If a table was not in the target database, gprestore returned an error. If the table existed in the database, gprestore replaced the existing table statistics. This is fixed. Now gprestore will restore statistics only for the tables that are restored.

gpbackup_manager v1.0.0

No changes since the previous release.

gpbackup_ddboost_plugin v1.2.0

No changes since the previous release.

gpbackup_s3_plugin v1.2.0

No changes since the previous release.

Known Issues

  • [169235299 - gprestore] When performing a filtered restore, for example using the --include-table option, gprestore attempts to create all schemas present in the original backup. If a schema already exists in the target database, gprestore logs a warning:
    [WARNING]:-Schema <schema name> already exists
  • Beginning with versions 4.3.33 and 5.19, Greenplum Database checks that the distribution key for a table is a prefix of any unique index key. This policy is not in place for Greenplum Database versions before 4.3.33 or 5.19, and it is possible to create a backup of a database from one of these earlier versions with unique indexes that do not comply with the policy. When you restore such a backup to a Greenplum Database version that does enforce the policy:
    • If the unique index is for a primary key constraint, Greenplum Database automatically modifies the table's distribution policy if the table has no data.
    • In other cases, creating a unique index with a key that does not begin with the table's distribution key fails.

    This issue affects restoring backups made from Greenplum Database 4.3.32.0, 5.18.0, or earlier to a Greenplum Database version 4.3.33.0, 5.19.0, 6.0, or later system. The issue affects the gprestore, gpdbrestore, and pg_restore utilities.

Release Numbering Conventions

The Pivotal Greenplum Backup and Restore distribution release number indicates the type of the release.

  • The first number is the gpbackup/gprestore major release number. For example, given the release number, 1.14.0-1, the major release number is 1.
  • The second number is the minor release number. Given the release number 1.14.0-1, the minor release number is 14. This number increments when new features are added to the gpbackup/gprestore utilities.
  • The third number is the gpbackup/gprestore maintenance release number. Given the release number 1.14.0-1, the maintenance release number is 0. The release contains gpbackup and gprestore version 1.14.0. The maintenance release number increments when the gpbackup/gprestore utilities are released with fixes, but without new features.
  • The fourth number is the maintenance release version for the Greenplum Backup and Restore distribution. Components included in the distribution, such as gpbackup_manager and the backup storage plugins, are numbered separately. If one or more included components is updated, a new distribution is released with this final number incremented. Release number 1.14.0-2, for example, is the second release of gpbackup/gprestore version 1.14.0, and indicates new versions of one or more of the components have been included in the release.