The Tanzu Greenplum Data Copy Utility is compatible with these Tanzu Greenplum versions:
Release Date: April 13, 2022
gpcopy version 2.3.2 is a maintenance release that includes changes and resolves several issues.
gpcopy now respects the case sensitivity of database, schema, and table names that you specify with
--dest-table options when you enclose the individual name in double quotes. For example:
gpcopy always transforms unquoted names to lower case.
gpcopy relaxes the
gpcopy_helper version check.
gpcopyupdates the version of
gothat it uses to build it's CLI tool to version 1.17.6 to mitigate CVE-2021-44716.
gpcopydid not respect the case-sensitivity of database, schema, and table names specified via the
--dest-tableoptions when the name was enclosed in double quotes.
gpcopydid not terminate queries and the helper daemon when it failed to create clean up files in the current working directory.
gpcopydid not print a summary report when a copy operation was cancelled with a Ctrl-C.
gpcopy version 2.3.1 is a maintenance release that resolves several 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.
 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).
 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.
 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.
 Fixed an issue where
gpcopy did not handle
DISTRIBUTED REPLICATED tables correctly, allowing duplicated data to be copied.
gpcopy version 2.3.0 is a minor release that adds features and resolves several issues.
--timeoutoption 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.
gpcopyincludes a list of tables and views that were successfully copied to the destination system in the text file
~/gpAdminLogsdirectory on the master host.
gpcopyfails to copy tables or views, the utility creates a text file
gpcopy_date_failure.listthat lists the failed tables or views in the
~/gpAdminLogsdirectory on the master host. After resolving issues that caused the failures, you can run
--include-table-fileoption to copy the tables or views that were not copied.
--parallelize-leaf-partitions=truefailed with the error message
gpcopydestination cluster was busy processing requests, the default
gpcopynetwork 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
--timeoutoption that allows changing the connection timeout. See Features.
gpcopylog files where "transaction" was misspelled as "trasaction" in several messages.
gpcopycould create numerous, large log files in the
/tmpdirectory and cause the copy operation to fail with a
no space left on deviceerror.
gpcopydid not correctly copy the sequence owner and privileges.
sql:JSON key, used with the
--include-table-jsonoption, is compatible only with Greenplum Database version 5.20 and later.