1.30.0

gpbackup 1.30.0

New Features
* When using gpbackup with Greenplum 7.0.0 or later, gpbackup writes
  both to standard output and to the log file the progress of the COPY
  command for each table.

* The include-table* and exclude-table* options now support schemas
  and tables containing a period in their name. The object containing
  the period must be set off in double quotes and the double quotes must
  be escaped.

* gpbackup now includes the database name in the subject line of the
  email.

* This release of gpbackup adds new fields to the backup file's metadata
  to facilitate parallel restores of predata metadata if the --jobs or
  --copy-queue-size options are invoked with gprestore. In addition,
  gpbackup now wraps predata restore statements in transactions to
  improve performance. Does not work with --on-error-continue.

* Add support for Enterprise Linux 9.

Changed Features

* When invoking the --backup-dir option, backup file directories are no
  longer categorized by segment. Instead, all backup files are now
  placed in a directory structure such as the following:
  backup-dir/backups/date/timestamp.

* When invoking the --include-table and --no-inherits options, only the
  table specified in the --include-table option is backed up, even if
  that table's DDL is dependent on other inherited tables.

Resolved Issue

* Resolves performance issues with an underlying catalog query when
  backing up INDEX information during a full backup.

1.29.4

gpbackup 1.29.4

Fixes:
* Updated query for external tables to match new behavior of GPDB7 GA.
* Improve query performance for renaming indexes on exchanged partitions
* Updated gppkg name for GPDB7, to keep consistency in package naming
  with GPDB6.

1.29.3

gpbackup 1.29.3

Fixes:
* Improve query performance for creating indexes and getting constraints

1.29.2

Only include table names in error_tables_metadata

As the error_tables_metadata file created by a failed gprestore is
intended to be used with --include-table and --exclude-table filters on
a subsequent restore, it should not include the names of any non-table
objects that failed to be restored.

1.29.1

gpbackup 1.29.1

Fixes:
* gprestore would previously fail with a critical error when attempting to
* write an error table file to a read-only directory where backups were stored.
* Now we log a warning and do not fail.

1.29.0

gpbackup 1.29.0

New Features

 * gpbackup includes a new command line option --no-inherits. When used together with the --include-table or --include-table-file options to back up a table, the metadata of the table's children and the metadata of any tables that share parents with this table are not backed up. For details, see the gpbackup reference topic.
 * When backing up using the --backup-dir, --metadata-only and --no-history options together, gpbackup now allows a backup to have the same timestamp as another backup, provided that each of the two backups has a distinct --backup-dir location.

Changed Features

 * gpbackup now logs information to the gpbackup_history.db database when the backup has failed or is terminated.
 * In addition to backing up children of tables included for backup gpbackup now also backs up any tables those children inherit.

Resolved Issues

 * [32872] Resolves an issue where backups based on a compression type of zstd could hang if zstd compression was not available on all the servers in the Greenplum cluster.

1.28.1

gpbackup 1.28.1

Features
* Added a new command line option --no-history: When used with gpbackup, metadata of the backup run
  is not written to the history database.
* Will log a Warning message, when the gpbackup_history.yaml file has not been migrated to the
  sqlite database: [WARNING]:-Legacy gpbackup_history file
  <MASTER_DATA_DIRECTORY>/gpbackup_history.yaml is still present. Please run 'gpbackup_manager
  migrate-history' to add entries from that file to the history database.

Fixes
* Incremental backup will not consider deleted backups when looking for most recent matching backup.

1.27.0

gpbackup 1.27.0

Features
* Beta support for backup and restore of GPDB7 databases.
    Restoring backups from earlier versions to GPDB7 is not yet supported.

Fixes
* Backup and restore of materialized views on GPDB6 and later now supported.
* Resolved an issue using resize-cluster with plugins in smaller-to-larger restores.
* Resolved an issue with hangs when restoring improperly packed backups in larger-to-smaller restores.

1.26.0

gpbackup 1.26.0

Features
* Users can now restore data to a cluster that has a different number of
segments than the cluster from which the data was backed up, using the
new --resize-cluster option. Only backups taken with gpbackup versions
>=1.26.0 support this feature.  This feature is currently considered to
be in beta.

Improvements
* Convert all usage of scp to rsync for increased security.

1.25.0

gpbackup 1.25.0

Features
* gpbackup can now export synchronized distributed snapshots, ensuring data consistency across
  parallel worker processes used per the --jobs option. As a result of this enhancement, the
  worker processes no longer need to hold ACCESS SHARE locks for the entire duration of the backup operation.
  NOTE: Requires Greenplum Database version 6.21 or higher

Improvements
* gpbackup no longer holds ACCESS SHARE locks on the segments. This
  significantly reduces the overall number of locks held for the
  duration of the backup operation and reduces the likelihood
  of exhausting shared memory on a segment.
  NOTE: Requires Greenplum Database version 6.21 or higher
* Tests now use Ginkgo 2.0 framework

Fixes
* Resolved an issue where implicit casts may cause backups to fail.
* Resolved an issue where applications that queried the gp_segment_configuration table were blocking because they were competing for connections.
* Resolved an issue where gpbackup_helper processes were lingering unnecessarily, rather than terminating.