Release Notes

Release Notes

Supported Platforms

The Pivotal Greenplum Data Copy Utility is compatible with these Greenplum Database versions:
  • Pivotal Greenplum Database 4.3.26 and later
  • Pivotal Greenplum Database 5.9 and later
  • Pivotal Greenplum Database 6.x

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