Supported Platforms

The Tanzu Greenplum Data Copy Utility is compatible with these Tanzu Greenplum versions:

  • Tanzu Greenplum Database 4.3.26 and later
  • Tanzu Greenplum Database 5.9 and later
  • Tanzu Greenplum Database 6.x

Version 2.4.1

Release Date: December 19, 2022

gpcopy version 2.4.1 is a maintenance release that includes a single bug fix.

Resolved Issues

  • [N/A] Resolves an issue where the gpcopy version 2.4.0 download packages available on VMware Tanzu Network were corrupt.

Version 2.4.0

Release Date: December 9, 2022

Tanzu Greenplum Data Copy Utility version 2.4.0 is a minor release that includes new features and a bug fix.

Features

gpcopy 2.4.0 includes the following new features:

  • gpcopy now supports SSL/TLS encryption on the data channel between the source and destination Greenplum Database clusters. This feature relies on an update to the gpcopy_helper utility. About SSL/TLS Encryption on the Data Channel describes how to direct gpcopy to use this encryption method.
  • When the pg_hba.conf file specifies password authentication, gpcopy can now obtain the connection password for the source and/or destination Greenplum Database user from the value of the PGPASSWORD or the PGPASSFILE environment variable; refer to About Connecting Using Password Authentication for more information.
  • When the pg_hba.conf file specifies the SSL/TLS connection type, gpcopy can now initiate an SSL-encrypted connection to the source and/or destination destination Greenplum Database cluster; refer to About Connecting Using SSL/TLS for more information and configuration information.

Resolved Issues

  • [32528] Resolves an issue where gpcopy returned the error relation <name> already exists when it failed to copy a partitioned table that was created with an explicit sequence column, and the owner of the sequence was since altered.

Version 2.3.2

Release Date: April 13, 2022

gpcopy version 2.3.2 is a maintenance release that includes changes and resolves several issues.

Changed Features

  • gpcopy now respects the case sensitivity of database, schema, and table names that you specify with --include-table[-xxx], --exclude-table[-xxx], and --dest-table options when you enclose the individual name in double quotes. For example:

    --include-table '"testdb"."Schema"."T1"'
    

    gpcopy always transforms unquoted names to lower case.

  • gpcopy relaxes the gpcopy_helper version check.

Resolved Issues

  • gpcopy updates the version of go that it uses to build it's CLI tool to version 1.17.6 to mitigate CVE-2021-44716.
  • [31760] Resolves an issue where gpcopy did not respect the case-sensitivity of database, schema, and table names specified via the --include-table[-xxx], --exclude-table[-xxx], and --dest-table options when the name was enclosed in double quotes.
  • [31680] Resolves an issue where gpcopy did not terminate queries and the helper daemon when it failed to create clean up files in the current working directory.
  • [30925] Resolves an issue where gpcopy did not print a summary report when a copy operation was cancelled with a Ctrl-C.

Version 2.3.1

gpcopy version 2.3.1 is a maintenance release that resolves several issues.

Resolved Issues

  • [n/a] To help with debugging, gpcopy now prints additional logging information:

    • The source and destination cluster versions are now displayed when the utility initializes at startup. For example:

      Initializing gpcopy
      Source cluster version: 6.9.0+dev.30.ge53fbea1b0 build dev
      Destination cluster version: 6.9.0+dev.30.ge53fbea1b0 build dev
      
    • The results of IP resolution for each destination segment are displayed the message: Resolving destination segments hostname IP address results.

  • [31467] Fixed an issue where the count validation could fail if the source and destination tables did not distribute the data in the same way (for example, for randomly-distributed tables).

  • [31467] Fixed a an issue that could cause a md5xor validation failure if a row had 64KB or more of CSV data.

    Note: You must update the gpcopy_helper utility to version 2.3.1 on every segment in order to apply this fix.

  • [31309] Fixed a crash that could occur if gpcopy did not have permission to write copy results to a file. The resulting crash could prevent the gpcopy_helper utility from terminating correctly on every segment.

  • [178122513] Fixed an issue where gpcopy did not handle DISTRIBUTED REPLICATED tables correctly, allowing duplicated data to be copied.

Version 2.3.0

gpcopy version 2.3.0 is a minor release that adds features and resolves several issues.

Features

  • The --timeout option specifies the maximum time in seconds to wait until both source and destination systems are ready for data transfer. The default is 30 seconds. A value of 0 deactivates the timeout.
  • For a copy operation, gpcopy includes a list of tables and views that were successfully copied to the destination system in the text file gpcopy_date_success.list in ~/gpAdminLogs directory on the master host.
  • If gpcopy fails to copy tables or views, the utility creates a text file gpcopy_date_failure.list that lists the failed tables or views in the ~/gpAdminLogs directory on the master host. After resolving issues that caused the failures, you can run gpcopy with the --include-table-file option to copy the tables or views that were not copied.

Resolved Issues

  • [30675] In some cases, copying an append-optimized partitioned table in parallel with the gpcopy options --truncate and --parallelize-leaf-partitions=true failed with the error message deadlock detected.
  • [30720, 30703] If the gpcopy destination cluster was busy processing requests, the default gpcopy network timeout of 5 seconds could result in panics caused by the utility using closed network connections. This issue is resolved by changing the default timeout to 30 seconds and adding the --timeout option that allows changing the connection timeout. See Features.
  • [30746] Resolved a typographical error in the gpcopy log files where "transaction" was misspelled as "trasaction" in several messages.
  • [30772] Resolved a problem where gpcopy could create numerous, large log files in the /tmp directory and cause the copy operation to fail with a no space left on device error.
  • [173678813] When copying a sequence, gpcopy did not correctly copy the sequence owner and privileges.

Known Issues and Limitations

  • The sql: JSON key, used with the --include-table-json option, is compatible only with Greenplum Database version 5.20 and later.
check-circle-line exclamation-circle-line close-line
Scroll to top icon