Release Notes

Release Notes

Release Date: February 21, 2020

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

Version 1.17.0

Pivotal Greenplum Backup and Restore version 1.17.0 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 Data Domain Boost for Data Domain Boost support information.

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

See Differences Compared to Open Source Greenplum Backup and Restore for the list of features that are only in Pivotal Greenplum Backup and Restore.

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

gpbackup v1.17.0

New Feature

  • Support for the options --include-schema-file and --exclude-schema-file that let you specify a text file containing a list of schemas to include or exclude from the backup operation.

Resolved Issues

  • [30361] gpbackup did not retain the schemas of leaf partitions of a partitioned table when the schemas were different than the root partition. Now the schema information is retained. See Requirements and Limitations for information about how leaf partition data is handled.
  • [30440] For some backup operations, gpbackup failed with the error missing FROM-clause entry for table <table>. The error occurred because gpbackup did not construct a valid query that was used to back up resource group information. This would cause gpbackup to return an error even if the database did not contain resource groups.
  • [171336948] gpbackup failed when backing up a database when MADlib is installed in the database. gpbackup failed when it incorrectly called the function version() from a schema that is referenced in the search_path instead of pg_catalog.version(). Now gpbackup calls pg_catalog.version().

gpbackup_helper v1.17.0

No changes since the previous release.

gprestore v1.17.0

New Features

  • Support for the options --include-schema-file and --exclude-schema-file that let you specify a text file containing a list of schemas to include or exclude from the restore operation.
  • Support for the --redirect-schema option. The option restores data in a specified schema instead of the original schemas. The specified schema must already exist. If the data being restored is in multiple schemas, all the data is redirected into the specified schema. This option must be used with an option that includes tables, --include-table or --include-table-file.
  • Support for a gprestore Beta feature, the option --incremental. This options restores only the table data in the incremental backup specified by the --timestamp option. Table data is not restored from previous incremental backups in the backup set. For information about incremental backups, see Creating and Using Incremental Backups with gpbackup and gprestore.

    When the --incremental option is specified gprestore truncates and reloads data in these cases:

    • Data updates to heap tables
    • Data updates to append-optimized tables
    • Data updates to leaf partitions
Warning: When this option is specified, gpbackup assumes that no changes have been made to the table definitions of the tables being restored.
Warning: This is a Beta feature and is not supported in a production environment.

Resolved Issues

  • [171336948] gprestore failed when restoring a database when MADlib is installed in the database. gpestore failed when it incorrectly called the function version() from a schema that is referenced in the search_path instead of pg_catalog.version(). Now gprestore calls pg_catalog.version().

gpbackup_manager v1.1.0

No changes since the previous release.

gpbackup_ddboost_plugin v1.2.0

No changes since the previous release.

gpbackup_s3_plugin v1.2.1

No changes since the previous release.

Data Domain Boost

This release of gpbackup and gprestore supports Data Domain Boost for backup on Red Hat Enterprise Linux. This table lists the supported versions of DDOS, Data Domain Boost SDK, and BoostFS.

Table 1. Data Domain Boost Compatibility
DDOS Data Domain Boost BoostFS
6.1 (all versions) 3.4 1.1
6.0 (all versions) 3.3 n/a
Note: In addition to the DDOS versions listed in the previous table, gpbackup and gprestore support all minor patch releases (fourth digit releases) later than the certified version.

Known Issues

  • A gprestore operation using the --redirect-schema option fails if gprestore attempts to restore an index in a schema and the name of the index is the name of the schema followed by a '.' (period). For example, this CREATE INDEX command creates the index named test. on a table in the schema test. The index is in the schema test.

    CREATE INDEX "test." ON test.mytbl USING btree (i);
    If the index and table are backed up with gpbackup, restoring the backup with this gprestore command fails because gprestore fails to restore the test. index.
    gprestore --timestamp <timestamp> --redirect-schema foo2
  • 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.

Differences Compared to Open Source Greenplum Backup and Restore

Pivotal Greenplum Backup and Restore includes all of the functionality in the open source Greenplum Backup github repository and S3 storage plugin repository and adds:

  • Greenplum backup plugin for DD Boost
  • Greenplum gpbackup_manager utility
  • Greenplum Backup and Restore installation file in gppkg format

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.16.0, the major release number is 1.
  • The second number is the minor release number. Given the release number 1.16.0, the minor release number is 16. This number increments when new features are added to the gpbackup/gprestore utilities.
  • The third number is the maintenance release number. This number increments when the gpbackup/gprestore utilities included in the distribution contain fixes without new features, or if one or more components included in the distribution, such as gpbackup_manager and the backup storage plugins, have been updated.

The release versions of the components included in the distribution, such as gpbackup_manager and the backup storage plugins, are separate from the distribution version, but follow the same numbering scheme as the distribution.