Release Notes

Release Notes

Updated: October 10, 2019

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

Version 1.14.0-1

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

A compressed tarball package for Pivotal Greenplum Backup and Restore has been added to Pivotal Network in this release. The tarball package can be installed on supported versions of Greenplum Database 4.3, 5, and 6.

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 Release Numbering Conventions for a description of the Pivotal Greenplum Backup and Restore release numbering scheme.

gpbackup v1.14.0

New Features

  • Improved performance on certain catalog queries specific to indexes.

Changed Features

  • Added additional logging to the gpbackup verbose output.
  • gpbackup --metadata-only now skips creation of segment directories as they are not needed.

Resolved Issues

  • [168143475] Resolves an "index out of range" error encountered during an incremental backup when no new data was present to backup.
  • [168385170] Resolves an issue in a GRANT statement when the ROLE in the GRANTED BY statement no longer exists in the system.

gpbackup_helper v1.14.0

Resolved Issues

  • [167661015] Resolves a scenario where the /tmp filespace is full and gpbackup_helper cannot successfully place a file in that directory.
  • [168324240] Resolves an issue where the table of contents file was not explicitly closed at the end of a gpbackup.

gprestore v1.14.0

New Feature

  • 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.

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

  • [169052763] You can create a full backup of a database with gpbackup using the --with-stats option to back up table statistics. However, when you try to restore only some of the tables and the statistics for the tables using gprestore with a table filter option and the --with-stats option, gprestore attempts to restore all the table statistics from the backup, not just the statistics for the tables being restored.When restoring all the table statistics, if a table is not in the target database, gprestore returns an error. If a table exists in the database, gprestore replaces the existing table statistics.
  • [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.
  • [29361] In Greenplum Database 4.3, if the server configuration parameter enable_mergejoin is set to on, gpbackup may fail with the following error:
    ERROR: Unexpected internal error (nodeMergejoin.c:1806) (SQLSTATE XX000)
  • 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, 5.18.0, or earlier to a Greenplum Database version, 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.