WIXLIB

Greenplum Database 4.3.24.0 Release NotesRelease Notes Pivotal 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 Store(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.24.0The table below lists issues that are now resolved in Pivotal Greenplum Database 4.3.24.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.24.0IssueNumberCategoryResolved InDescription4529QueryOptimizer4.3.24.0GPORCA generated an invalid plan for some queriesthat contain a non-redistributable column when the querycontains a join on the column, or when the DISTINCTkeyword is applied to the column, or when an aggregateincludes the column. The invalid plan returned an errorduring query execution.This issue has been resolved. GPORCA has beenimproved to not generate plans that contain a redistributemotion on a non-redistributable column.29265QueryOptimizer4.3.24.0For some queries that qualify tables with the ONLYkeyword, GPORCA returned incorrect results.This issue has been resolved. Now GPORCA falls backto legacy planner and returns the correct results for thespecified type of query.29257Backup/Restore4.3.24.0A restore operation performed by the gprestore utilityfailed when the backup contained a table column withcomment text and the text contained a single quote (').The utility did not correctly handle the single quote.This issue has been resolved. Now the utility correctlyhandles comment text that contains single quotes.6

Greenplum Database 4.3.24.0 Release NotesRelease NotesIssueNumberCategoryResolved InDescription29249QueryOptimizer4.3.24.0GPORCA produced wrong results for some queries whenthe query contains multiple predicates combined by AND orOR operators and where some of the predicates includeda NOT operator (NOT condition) . GPORCA did notprocess the NOT operator correctly.This issue has been fixed. GPORCA has been enhanced tocorrectly process the NOT operator for the specified type ofquery.29243gpfdist/gpload4.3.24.0In some cases, the gpfdist utility did not complete (hung)when accessing a named pipe and no read or write activityoccurs. The gpload utility did not properly terminate agpfdist process that has completed processing data.This issue has been resolved. Thegpload terminationprocess for gpfdist processes that have completedprocessing data has been improved. Also, the gpfdistutility now supports the GPFDIST WATCHDOG TIMERenvironment variable to help debug gpfdist hangs. SeeChanged Features.29235QueryOptimizer4.3.24.0For some queries with multiple joins, GPORCA wasincorrectly producing a distribution specification of a jointhat contained circular references. This caused GPORCAto go into an infinite loop and caused Greenplum Databaseto generate a segmentation fault.This issue has been resolved. GPORCA has beenenhanced to avoid distribution specifications with circularreferences.29206QueryPlanner4.3.24.0For some queries that contained window functions andpredicates, legacy query planner created a query plan thatdid not push the predicate below the window function whenappropriate. This caused a performance regression.This issue has been resolved. The predicate pushdownevaluation performed by query planner has been improvedfor the specified type of query.29201QueryOptimizer4.3.24.0For some queries against partitioned tables, GPORCAreturned a row count but did not return any data. Thiswas caused when GPORCA generated a query plan thatincorrectly materialized a join that contained a dynamictable scan.This issue has been resolved. GPORCA has beenimproved to avoid generating a plan that materializes a joinin the specified situation.7

Greenplum Database 4.3.24.0 Release NotesRelease NotesIssueNumberCategoryResolved InDescription29089gpssh4.3.24.0The Greenplum Database utilities gpssh-exkeys andgpseginstall failed when they were run on a hostsystem running RHEL 7.4 with FIPS enabled. The utilitiesdid not support the FIPS-compatible SSH key exchangealgorithm.This issue has been resolved. The Python paramiko libraryin Greenplum Database Python installation has beenupgraded to support newer SSH key exchange algorithms.See Changed Features.156019082QueryPlanner4.3.24.0The Greenplum Database legacy query planner did notprocess the NOT operator correctly for queries that containan expression of the form NOT (expression) in theWHERE clause, and the expression contains SELECTstatement.This issue has been resolved. Now the legacy queryplanner processes the NOT operator correctly for thespecified type of query.Known Issues in Greenplum Database 4.3.24.0This section lists the known issues in Greenplum Database 4.3.24.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 Zone8

Greenplum Database 4.3.24.0 Release NotesRelease NotesTable 3: All Known Issues in og andMetadataGreenplum Database does not acquire a lock on a schema whencreating a table inside the schema. A concurrent DROP of the schemaand CREATE TABLE operation will result in a leaked object (anorphan table or orphan relation columns) in the system catalog andpossibly on disk. For example, a relation created with this commandCREATE TABLE mytest.foobar (col1 int)during a concurrent DROP of the schema mytest might leak eitherthe table itself or the col1 attribute object.These leaked objects do not affect any future queries. The cataloginconsistencies can be detected with the gpcheckcat utility.Workaround: To block a concurrent DROP from occurring, acquireand hold a ROW SHARE lock on the row of the pg namespacecatalog table that corresponds to the schema. For example, thistransaction acquires a ROW SHARE lock on the pg namespacecatalog table row for the schema my schema.begin;SELECT nspname FROM pg namespace WHERE nspname 'my schema' FOR SHARE;.end;During the transaction, the lock prevents the schema from beingdropped.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.9

Greenplum Database 4.3.24.0 Release NotesRelease NotesIssueCategoryDescription28947AccessMethodsA 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.26675gpcrondumpDuring 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.10

Greenplum Database 4.3.24.0 Release NotesRelease temFor 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.25584QueryExecutionIn 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.11

Greenplum Database 4.3.24.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.12

Greenplum Database 4.3.24.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 its parts (child tables).20241QueryOptimizerThe GPORCA does not consider indices when querying parts/childtables of partitioned tables directly.25326InterconnectSetting the Greenplum Database server configuration parameterlog hostname to on Greenplum Database segment hosts causesan Interconnect Error that states that the listeneraddress name orservice not known.The parameter should be set to on only on the Greenplum Databasemaster.25280ManagementThe Greenplum Database utility gpstop, the utility returns an errorScripts: gpstart/ if it is run and the system environment variable LANG is set, forgpstopexample, export LANG ja JP.UTF-8.Workaround: Unset the environment variable LANG before runningthe gpstop utility. For example: unset LANG25246ManagementScripts:gpconfigWhen you set the server configuration parameters gp emailto and gp email from with the Greenplum Database utilitygpconfig, the utility removes the single quotes from the values. gpconfig -c gp email to -v 'test@example.com'The improperly set parameter causes Greenplum Database to failwhen it is restarted.Workaround: Enclose the value for gp email to or gp emailfrom with double quotes. gpconfig -c gp email to -v "'test@example.com'"13

Greenplum Database 4.3.24.0 Release NotesRelease ProcessesWhen the server configuration parameter client min messagesis set to either set to PANIC or FATAL and a PANIC or FATAL levelmessage is encountered, Greenplum Database hangs.The client min messages parameter should not be set a valuehigher than ERROR.24588ManagementScripts:gpconfigThe Greenplum Database gpconfig utility does not display thecorrect

For previous versions of the release notes for Greenplum Database, go to Pivotal Greenplum Database Documentation. For information about Greenplum Database end of life, see Pivotal . 2.1.0.0 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. .