WIXLIB

Greenplum Database 4.3.18.0 Release NotesRelease NotesFor NetBackup Client version 7.1, Greenplum Database supports only NetBackup Server Version7.5.Greenplum Database uses the NetBackup API (XBSA) to communicate with the NetBackup.Greenplum Database uses SDK version XBSA 1.1.0.Greenplum Database support for NetBackup Client version 7.1 is deprecated. The NetBackup SDKlibrary files for NetBackup version 7.1 will be removed from the Greenplum Database installation ina future release.Greenplum Database support on DCA: Greenplum Database 4.3.x, all versions, is supported on DCA V3.Greenplum Database 4.3.x, all versions, is supported on DCA V2, and requires DCA software version2.1.0.0 or greater due to known DCA software issues in older DCA software versions.Greenplum Database 4.3.x, all versions, is supported on DCA V1, and requires DCA software version1.2.2.2 or greater due to known DCA software issues in older DCA software versions.Informatica PowerCenter 10.2 and 9.x are certified with Greenplum Database 4.3.x, all versions.Note: Greenplum Database 4.3.18.0 does not support the ODBC driver for Cognos Analytics V11.In the next major release of Greenplum Database, connecting to IBM Cognos software with anODBC driver will not be supported. Greenplum Database supports connecting to IBM Cognossoftware with a JDBC driver.Pivotal recommends that you migrate to a version of IBM Cognos software that supportsconnectivity to Greenplum Database with a JDBC driver.Supported Platform NotesImportant: When data loss is not acceptable for a Pivotal Greenplum Database cluster, masterand segment mirroring must be enabled in order for the cluster to be supported by Pivotal. Withoutmirroring, system and data availability is not guaranteed, Pivotal will make best efforts to restore acluster in this case. For information about master and segment mirroring, see About Redundancyand Failover in the Greenplum Database Administrator Guide.The following notes describe platform support for Greenplum Database. Please send any questions orcomments to Pivotal Support at https://support.pivotal.io. The only file system supported for running Greenplum Database is the XFS file system. All other filesystems are explicitly not supported by Pivotal.Greenplum Database is supported on all 1U and 2U commodity servers with local storage. Specialpurpose hardware that is not commodity may be supported at the full discretion of Pivotal ProductManagement based on the general similarity of the hardware to commodity servers.Greenplum Database is supported on network or shared storage if the shared storage is presentedas a block device to the servers running Greenplum Database and the XFS file system is mountedon the block device. Network file systems are not supported. When using network or sharedstorage, Greenplum Database mirroring must be used in the same way as with local storage, and nomodifications may be made to the mirroring scheme or the recovery scheme of the segments. Otherfeatures of the shared storage such as de-duplication and/or replication are not directly supported byPivotal Greenplum Database, but may be used with support of the storage vendor as long as they donot interfere with the expected operation of Greenplum Database at the discretion of Pivotal.Greenplum Database is supported when running on virtualized systems, as long as the storageis presented as block devices and the XFS file system is mounted for the storage of the segmentdirectories.A minimum of 10-gigabit network is required for a system configuration to be supported by Pivotal.Greenplum Database is supported on Amazon Web Services (AWS) servers using either Amazoninstance store (Amazon uses the volume names ephemeral[0-20]) or Amazon Elastic Block Store6

Greenplum Database 4.3.18.0 Release NotesRelease Notes (Amazon EBS) storage. If using Amazon EBS storage the storage should be RAID of Amazon EBSvolumes and mounted with the XFS file system for it to be a supported configuration.For Red Hat Enterprise Linux 7.2 or CentOS 7.2, the default systemd setting RemoveIPC yesremoves IPC connections when non-system users logout. This causes the Greenplum Databaseutility gpinitsystem to fail with semaphore errors. To avoid this issue, see "Setting the GreenplumRecommended OS Parameters" in the Greenplum Database Installation Guide.Resolved Issues in Greenplum Database 4.3.18.0The table below lists issues that are now resolved in Pivotal Greenplum Database 4.3.18.0For issues resolved in prior 4.3 releases, refer to the corresponding release notes. Release notes areavailable from the Pivotal Greenplum page on Pivotal Network or on the Pivotal Greenplum Databasedocumentation site at Release Notes. A consolidated list of resolved issues for all 4.3 releases is alsoavailable on the documentation site.Table 2: Resolved Issues in 4.3.18.0IssueNumberCategoryResolved InDescription29117QueryPlanner4.3.18.0When an INSERT command contains a subquery thatcontains a window function, and the INSERT predicatecontains a qualifier that refers to the window function, thelegacy optimizer incorrectly pushed down the qualificationand generated an error.This issue has been resolved. In the legacy optimizer,checking for predicate push down has been improved.29110Catalog andMetadata4.3.18.0In some cases, after splitting a leaf partition of a multi-levelpartitioned table with the ALTER TABLE command with thePARTITION SPLIT clause, inserting data into the tablereturned the error no partition for partitioningkey. The insert error occurred because GreenplumDatabase did not update the partitioned table metadatacorrectly when splitting the leaf partition.This issue has been resolved. Greenplum Database hasimproved the managing of table metadata when splitting aleaf partition.29099Backup andRestore4.3.18.0The Greenplum Database gpdbrestore utility failed whenthe table data contains an SQL command. For example,the text SET search path demo has been insertedinto a table that has been backed up. The gpdbrestoreutility fails when it attempted to restore the table.This issue has been resolved. Now the utility can restoretables that contain SQL commands.7

Greenplum Database 4.3.18.0 Release NotesRelease NotesIssueNumberCategoryResolved InDescription29092QueryOptimizer4.3.18.0GPORCA generated a PANIC when generating a plan forquery that contains a function that is nested in a windowfunction. Greenplum Database does not support queriesthat contain a function that is nested in a window function.This issue has been resolved. Now Greenplum Databasereturns an error for the specified type of queries.29083DLL4.3.18.0If the default table storage options specified by theserver configuration parameter gp default storageoptions are different than the storage options that aredefined for a table, altering the table with an ALTER TABLEcommand with the REORGANIZE TRUE clause, mightcorrupt the table data. For example, after creating a table,changing gp default storage options so that thedefault table storage orientation is column, and then usingthe ALTER TABLE command with the REORGANIZE TRUEclause.The issue occurred because the ALTER TABLE commandwith the REORGANIZE TRUE clause did not recognizethe correct table storage options during table datareorganization.This issue has been resolved. The ALTER TABLEcommand detects the correct table storage options duringtable data m Database does not support splitting a leaf childpartition of a partition table if the leaf partition is defined aslist partition. However, in some cases, attempting to split alist partition caused a Greenplum Database PANIC.This issue has been resolved. Now Greenplum Databasereturns an error for the specified situation.29061gpcheckcat4.3.18.0In some cases, the Greenplum Database gpcheckatutility returned an error stating that a value was out ofrange for type integer when the utility did not handle large31OID values correctly (relfile nodes exceeding 2 , morethan 2 billion).This issue has been resolved. Now the utility handles largeOID values correctly.29046QueryExecution4.3.18.0For some group aggregate queries with a GROUP BYclause that contains a CUBE and also specify a HAVINGclause, Greenplum Database generated a PANCIC.The PANIC was generated during aggregation whenGreenplum Database did not handle a NULL case properly.This issue has been resolved. For the specified type ofqueries, the handling of NULL cases during aggregationhas been improved.8

Greenplum Database 4.3.18.0 Release NotesRelease NotesIssueNumberCategoryResolved InDescription29012gpload4.3.18.0In some cases, the Greenplum Database utility gploadrecorded the incorrect number of rejected rows whenloading data the when utility was configured to log errors.The utility did not properly record errors from multipleGreenplum Database segment instances.This issue has been resolved. Now the utility correctlyrecords errors from multiple segments.29009gprecoverseg 4.3.18.0Running the Greenplum Database gprecoverseg withthe option -r to rebalance segments did not return errorsif the operation generated errors on some segments andcompleted successfully on other segments.This issue has been resolved. Now if any errors occurduring a rebalance operation, the user is notified and isreferred to the logs for details.26956QueryOptimizer4.3.18.0For some queries, GPORCA did not choose a query planwith bitmap index scan when a bitmap index on a columncould be used as a filter condition in the query. This causeda performance degradation when comparing GPORCA withthe legacy query planner.This issue has been resolved. Now GPORCA chooses thefaster plan with the bitmap index scan.23438gpcheckcat4.3.18.0The Greenplum Database gpcheckcat utility testmissing extraneous returned incorrect results whenthe test found database catalog inconsistencies. The testdid not process the inconsistencies correctly.This issue has been resolved. Now the utility returnscorrect results when the test finds catalog e queries that perform in-memory operationsgenerated an invalid memory alloc requesterror for some values of the statement mem serverconfiguration parameter. The error was caused when an inmemory operation exceeded a maximum allowed numericvalue.This issue has been resolved. The maximum allowed valuehas been increased to avoid the error.150243109QueryOptimizer4.3.18.0GPORCA generated a PANIC when generating a plan forqueries where the predicate performs a comparison of twosubqueries, and the comparison also uses the clause ANY,ALL, IN, or NOT IN. GPORCA did not properly handle thesubquery in left side of the comparison.This issue has been resolved. Now GPORCA generates aplan successfully.9

Greenplum Database 4.3.18.0 Release NotesRelease NotesKnown Issues in Greenplum Database 4.3.18.0This section lists the known issues in Greenplum Database 4.3.18.0. A workaround is provided whereapplicable.For known issues discovered in previous 4.3.x releases, see the release notes available from the PivotalGreenplum page on Pivotal Network or on the Pivotal Greenplum Database documentation site at ReleaseNotes. For known issues discovered in other previous releases, including patch releases to GreenplumDatabase 4.2.x, 4.1 or 4.0.x, see the corresponding release notes, available from Dell EMC Support ZoneTable 3: All Known Issues in 4.3.18.0IssueCategoryDescription152327383Backup andRestoreThe Greenplum Database backup and restore utilities gpcrondump,gpdbrestore, pg dump, and pg restore can back up and restoresingle-level partitioned tables partitioned tables that have beenaltered by exchanging a leaf child partition with a readable externaltable only when the partitions are named partitions (partitionnamein the pg partitions system view is not NULL for the partition).151135629COPYWhen the ON SEGMENT clause is specified, the COPY commanddoes not support specifying a SELECT statement in the COPY TOcommand. However, this command completes successfully, but thefiles are not created on the segment hosts.COPY (SELECT * FROM testtbl)TO '/tmp/mytst SEGID ' ON SEGMENT150625402SessionManagementWhen the server configuration parameter gp strict xml parseis set for a session and the session is idle for longer than gp vmemidle resource timeout, the value of gp strict xml parsechanges back to the value set for the system (or the database if theparameter is set for the database).29064Storage: DDLThe money datatype accepts out-of-range values as negative values,and no error message is displayed.Workaround: Use only in-range values for the money datatype (32bit for Greenplum Database 4.x, or 64-bit for Greenplum Database 5.x). Or, use an alternative datatype such as numeric or decimal.28947AccessMethodsA deadlock might occur on an append-optimized columnar tablewhen a VACUUM operation and an INSERT operation are performedconcurrently on the table.Workaround: If a deadlock condition occurs, terminate the INSERToperation to break the deadlock. To eliminate the possibility ofencountering this issue, avoid concurrent VACUUM and INSERToperations.10

Greenplum Database 4.3.18.0 Release NotesRelease NotesIssueCategoryDescription26675gpcrondumpDuring the transition from Daylight Saving Time to Standard Time,this sequence of events which might cause a gpcrondump backupoperation to fail.If an initial backup is taken between 1:00AM and 2:00AM DaylightSaving Time, and a second backup is taken between 1:00AM and2:00AM Standard Time, the second backup might fail if the firstbackup has a timestamp newer than the second.Pivotal recommends performing only a single backup between thehours of 1:00AM and 2:00AM on the days when the time changes: November 5, 2017November 4, 2018November 3, 2019If the failure scenario is encountered, it can be remedied by restartingthe backup operation after 2:00AM Standard Time.146542311gploadWhen running the Greenplum Database utility gpload on AIXsystems, the utility returns an error if the YAML control file forutility contains a line that specifies the \ (backslash) as the escapecharacter, ESCAPE: '\'. The error states that the \ at the end of astring could not be decoded.Workaround: To avoid the error, remove the line from the file, orspecify the line without a character, ESCAPE:. The \ character is thedefault escape character. The line is not required in the file.142743943S3 ExternalTablesThe s3 protocol might not handle the header row in data filesproperly in this situation: A readable external table is defined with the s3 protocol and theHEADER option.The external table has been exchanged to be a leaf child table ofa partitioned table.Queries against the partitioned table might return an error.26591QueryExecutionFor the Greenplum Database function get ao compressionratio(), specifying a null value or the name of table that containsno rows causes a Greenplum Database PANIC.Workaround: Specify a non-null value or a table that contains rows.115746399OperatingSystemFor Greenplum Database that is installed on Red Hat EnterpriseLinux 7.x or CentOS 7.x prior to 7.3, an operating system issue mightcause Greenplum Database that is running large workloads to hangin the workload. The Greenplum Database issue is caused by Linuxkernel bugs.Workaround: RHEL 7.3 and CentOS 7.3 resolves the issue.26626GPHDFSFor Greenplum Database external tables, the gphdfs protocolsupports Avro files that contain a single top-level schema. Avro filesthat contain multiple top-level schemas are not supported.11

Greenplum Database 4.3.18.0 Release NotesRelease NotesIssueCategoryDescription25584QueryExecutionIn some situations, a running Greenplum Database query cannotbe terminated with the functions pg cancel backend or pgterminate backend.The functions could not terminate the query due to a blocking fopenof a FIFO file for write.26249GPHDFSWhen reading data from an Avro file, the gphdfs protocol does notsupport the double quote character (") within string data. The gphdfsprotocol uses the double quote as the column delimiter.Workaround: Before reading data from an Avro file, either removedouble quotes that are in string data or replace the character with adifferent character.26292Loaders: gpload The Greenplum Database gpload utility fails on MacOS X ElCapitan. The utility script is included with the Greenplum DatabaseLoad Tools installer package for Apple OS X greenplumloaders-version-OSX-i386.bin.Workaround: Run the python script gpload.py directly. Forexample, python command displays the gpload help information onthe command line.python gpload.py -h26128Loaders: gpload When the YAML control file for the Greenplum Database gploadutility specifies the key LOG ERRORS: true without the key REUSETABLES: true, the gpload operation returns only summaryinformation about formatting errors. The formatting errors are deletedfrom Greenplum Database error logs. When REUSE TABLES: trueis not specified, the temporary tables that are used by gpload aredropped after the gpload operation, and the formatting errors arealso deleted from the Greenplum Database error logs.Workaround: Specify the YAML control file key REUSE TABLES:true to retain the temporary tables that are used to load the data.The log information is also retained. You can delete the formattingerrors in the Greenplum Database logs with the Greenplum Databasefunction gp truncate error log().For information about the gpload utility, see the GreenplumDatabase Utility Guide.12

Greenplum Database 4.3.18.0 Release NotesRelease r queries that compare data from columns of different charactertypes, for example a join comparing a columns of data typesCHAR(n) and VARCHAR(m), the returned results might not be asexpected depending the padding added to the data (space charactersadded after the last non-space character).25936Query PlannerFor example, this comparison returns false.select 'A '::char(2) 'A '::text ;This comparison returns true.select 'A'::char(2) 'A '::varchar(5) ;Workaround: Pivotal recommends specifying character columntypes to be of data type VARCHAR or TEXT so that comparisonsinclude padding added to the data.For information about how the character data types CHAR, VARCHAR,and TEXT handle padding added to the data see the CREATE TABLEcommand in the Greenplum Database Reference Guide.25737Catalog andMetadataGreenplum Database does not support the FILTER clause withinaggregate expressions.25754ManagementScripts:expansionThe Greenplum Database gpexpand utility fails to create an inputfile for system expansion if the Greenplum Database system definedifferent TCP/IP port numbers on different hosts for GreenplumDatabase internal communication.Workaround: Create the input file manually.25833ManagementScripts:gpexpandThe Greenplum Database utility gpexpand fails when expandinga Greenplum Database system and in the system a database tablecolumn name contains a tab character. The utility does not supportdatabase names, table names, or column names that contain a tabcharacter.15835DDL and UtilityStatementsFor multi-level partitioned tables that have these characteristics: The top level partition is partitioned by range.The lowest level partition (the leaf child partitions) are partitionedby list.Splitting a subpartition with the ALTER TABLE SPLIT PARTITIONcommand returns an error and rolls back the transaction.12019ManagementScripts:checkperfWhen the Greenplum Database gpcheckperf utility is run with theoption -f host file and the host that is running gpcheckperf islisted in host file, processes that were started gpcheckperf mightnot be cleaned up after the utility completes.Workaround: Manually stop the processes that were started bygpcheckperf.13

Greenplum Database 4.3.18.0 Release NotesRelease ORCA might terminate all sessions if a query attempts to cast to atimestamp a date with year greater than 200,000.23571QueryOptimizerFor queries that contain inequality conditions such as ! , and , ,GPORCA does not consider table indexes when generating a queryplan. For those queries, indexes are not used and the query mightrun slower than expected.21508QueryOptimizerGPORCA does not support GiST indexes.20030QueryOptimizerGPORCA does not support partition elimination when the querycontains functions that are applied to the partition key.20360QueryExecutionGPORCA does not enforce different access rights in different parts ofa partition table. Pivotal recommends that you set the same accessprivileges for the partitioned table and all

1.2.2.2 or greater due to known DCA software issues in older DCA software versions. Informatica PowerCenter 10.2 and 9.x are certified with Greenplum Database 4.3.x, all versions. Note: Greenplum Database 4.3.18.0 does not support the ODBC driver for Cognos Analytics V11. Greenplum Database. 18. to: 1)