Greenplum Database 4.3.x Resolved Issues

A newer version of this documentation is available. Click here to view the most up-to-date release of the Greenplum 4.x documentation.

Greenplum Database 4.3.x Resolved Issues

Consolidated list of resolved issues for the Greenplum Database 4.3.x releases.

4.3.4.x Releases

Table 1. Resolved Issues in 4.3.4.x
Issue Number Category Resolved In Description
25422 Management Scripts: General 4.3.4.2 The Greenplum Database utility gprecoverseg returned an error when the PGPORT environment variable was not set.
25417 Monitoring: gpperfmon server 4.3.4.2 In some cases when the Greenplum Command Center is installed, the gpsmon process timed out after one hour and returned an error that no request were received after 3600 seconds.
0561896 Management Scripts: recoverseg 4.3.4.2 In Greenplum Database 4.3.4.1, the Greenplum Database gprecoverseg utility checked persistent tables by default. In some cases, this check reported false positives for catalog corruptions.

For this release, the persistent table checks have been removed from gprecoverseg. To check for persistent table issues, use the Greenplum Database gpcheckcat utility.

The behavior in Greenplum Database 4.3.4.2 has been reverted to the behavior in 4.3.4.0 and earlier.

25202 Management Scripts: gpstart/gpstop 4.3.4.1 The Greenplum Database utility gpstop did not clean up shared memory after stopping segments.
25201 Storage: Access Methods 4.3.4.1 A Greenplum Database PANIC occurred when altering a column and adding a new column in the same command on an append-optimized column-oriented table.
25193 Query Execution 4.3.4.1 In some cases, a PL/pgSQL exception handler disabled sequence access for a query. This caused Greenplum Database to return an error if the same query required a new sequence value after the PL/pgSQL exception.
25192 Storage: Transaction Management 4.3.4.1 For some queries that create sub-transactions, a fix in an earlier release degraded performance.

The performance degradation issue has been resolved.

25162 Storage: Access Methods 4.3.4.1 In previous releases, the Greenplum Database server configuration parameter gp_appendonly_compaction_threshold was not visible. This issue has been resolved.

For information about the parameter, see "Server Configuration Parameters" in the Greenplum Database Reference Guide.

25082 Languages: R PLR 4.3.4.1 The Greenplum Database utility gpssh supports the -s option to source the file greenplum_path.sh before executing any commands on the target host.

For information about the utility, see the Greenplum Database Utility Guide.

25066 Storage: Access Methods 4.3.4.1 In some cases, a Greenplum Database PANIC occurred when a query performed an index scan on an append-optimized table that was populated with concurrent inserts followed by updates or deletes.
25029 Upgrade / Downgrade 4.3.4.1 In some cases, the Greenplum Database utility gpmigrator_mirror failed when upgrading from 4.2.x to 4.3.x.
25017 Monitoring: gpperfmon server 4.3.4.1 In some cases, high memory consumption spikes were caused by gpmon. The memory consumption spikes might have caused gpmmon segmentation faults.

The Greenplum Database Command Center parameter ignore_qexec_packet reduces the spikes of memory consumption. See the Greenplum Command Center Administrator Guide.

25004 Upgrade / Downgrade 4.3.4.1 In Greenplum Database 4.3.3 and later, the GRANT and REVOKE commands support the TRUNCATE privilege on a table. The upgrade process to a release between 4.3.3 and 4.3.4 did not grant the TRUNCATE permission to database tables that were created before the upgrade.

This issue has been resolved when upgrading to 4.3.4.1.

24964 Management Scripts: recoverseg 4.3.4.1 The Greenplum Database utility gprecoverseg did not ensure segments were stopped before attempting segment recovery.
24899 Functions and Languages 4.3.4.1 The aggregation function sum failed when the function arguments are empty arrays.
24898 Management Scripts: recoverseg 4.3.4.1 The Greenplum Database utility gprecoverseg failed when Greenplum Database persistent tables contained inconsistencies.

Now, before attempting a segment recovery, the utility checks for persistent table inconsistencies and returns an error when inconsistencies are found.

24841 Storage: Access Methods 4.3.4.1 Running an UPDATE command after a DROP COLUMN and ADD PARTITION command on a partitioned table caused a Greenplum Database segment instance failure.
24740 Storage: Segment Mirroring 4.3.4.1 In some cases, interrupts that occurred during Greenplum Database query processing were not handled properly. This caused an increase in CPU utilization and a decrease in performance.
24678 Storage: Segment Mirroring 4.3.4.1 A performance issue was found with Greenplum Database during table scans. In some cases, unnecessary network traffic and increased disk activity occurred during read operations during the table scan.
24632 Catalog and Metadata 4.3.4.1 A SELECT command failed on a table if the table was defined with DISTRIBUTED BY clause that contained more than 200 columns.

This issue has been resolved.

24563

20470

Query Planner 4.3.4.1 For some queries that required a correlated subquery, Greenplum Database generated a query plan that caused a segmentation fault when the plan was executed.

This issue has been resolved.

24505 Management Scripts: recoverseg 4.3.4.1 The Greenplum Database utility gprecoverseg did not properly handle a segment that was in a transition phase, for example the primary segment is down and the mirror segment has not yet become the primary.

Now the utility retries segment recovery in this situation.

23267 Functions and Languages 4.3.4.1 Memory leaks in the Greenplum Database aggregate functions string_agg and array_agg have been fixed.
21724 Query Planner 4.3.4.1 Greenplum Database executes an SQL query in two stages if a scalar subquery is involved. The output of the first stage plan is fed into the second stage plan as a external parameter. If the first stage plan generated zero tuples and directly contributed to the output of the second stage plan, incorrect results might have been returned.

This issue has been resolved.

17709 Catalog and Metadata 4.3.4.1 When the Greenplum Database utility gpcheckcat was run with the -A option to check all databases, the utility overwrote repair scripts for each database.

This issue has been resolved.

24913 Storage Access Methods 4.3.4 In some cases, after a VACUUM operation was performed on an append-optimized table that contains an index, SQL queries that were run against the table returned incorrect data.
24778 Security 4.3.4 Greenplum Database software has been updated to use OpenSSL 0.9.8zc in response to the OpenSSL Security Advisory [15 Oct 2014]. For information about the advisory, see http://www.openssl.org/news/secadv_20141015.txt
24770 Dispatch 4.3.4 In some cases, NULL pointer handling was not performed correctly during query execution. This caused a panic on Greenplum Database master.
24694 Upgrade / Downgrade 4.3.4 The attribute name of a visimap metadata table for append-optimized tables was incorrectly named during the upgrade to 4.3.x from Greenplum Database 4.2.x.

This issue has been resolved.

24693   4.3.4 For the visimap metadata table for append-optimized tables, the value of attstorage was set incorrectly in the pg_attribute table during the upgrade to 4.3.x from Greenplum Database 4.2.x.

This issue has been resolved.

24692 Upgrade / Downgrade 4.3.4 A unnecessary record for the internal built-in function pg_get_stat_walsenders was added to the pg_depend table during the upgrade to 4.3.x from Greenplum Database 4.2.x.

This issue has been resolved.

24684 Locking, Signals, Processes 4.3.4 In some cases, Greenplum Database did not clean up processes correctly during a commit transaction. This caused crash recovery issues after a Greenplum Database restart of both a primary segment and its mirror segment.
24683 Backup and Restore 4.3.4 There were performance issues when backing up specific tables from Greenplum Database using the Greenplum Database utility gpcrondump with the --table-file, -t, or --exclude-table-file, -T options.

The back up performance has been improved.

24679 Locking, Signals, Processes 4.3.4 In some cases, Greenplum Database PL/Java did not exit properly and caused crash recovery issues after a Greenplum Database restart of both a primary segment and its mirror segment.
24677 Backup and Restore 4.3.4 In some cases after a successful back up operation, error messages about lock files were incorrectly displayed.

This issue has been resolved.

24667 Build, Test 4.3.4 When creating a temporary table with the ON COMMIT DELETE ROWS clause in a heavy workload environment, the prepared transaction that created the temporary table failed in some cases.
24662 Upgrade/Downgrade 4.3.4 The privilege of the internal system view pg_stat_walsenders was set to NULL during the upgrade to 4.3.x from Greenplum Database 4.2.x.

The upgrade process now sets the privilege correctly.

24630 Management Scripts: gpsd 4.3.4 The Greenplum Database support utility gpsd has been enhanced to be more memory efficient in order to prevent failures when used on a database that contains large schemas.
24606 Storage access method 4.3.4 In some cases, queries that were run against the gp_toolkit view gp_size_of_table_and_indexes_disk returned an error when the queries are run concurrently with DDL statements.
24515 Replication: Segment Mirroring 4.3.4 In some cases under a heavy workload, logging onto the Greenplum Database segment host as a UNIX user was not possible. This was caused by a Greenplum Database filerep process that was incorrectly sending signals to the user after the process failed to create a sub-process.
24383 GPHDFS 4.3.4 Greenplum Database external tables did not support using the gphdfs protocol and MapR to access HDFS data.
24264 Catalog and Metadata 4.3.4 The commands REINDEX TABLE table_name and REINDEX INDEX index_name did not re-index child partition indexes of a partitioned table.
24216 Management Scripts: gpstart/gpstop 4.3.4 In some cases, the Greenplum Database utility gpstop failed to shutdown a database.
24052 Query Planner 4.3.4 In some cases, when executing a query that joined tables and the tables have extremely inaccurate statistics, Greenplum Database would return an error that reported being out of memory.

This issue has been resolved.

24003 Dispatch, Interconnect 4.3.4 In some cases, executing an SQL query caused a memory leak.
23802 Query Execution 4.3.4 Greenplum Database did not manage temporary workfiles (spill files) properly. In some cases, this caused a query that required workfiles to fail with a message that stated that a Greenplum Database segment had reached the maximum configured workfile usage limit.
23751 Monitoring: gpperfmon server 4.3.4 In some cases, a memory leak caused the gpmmon process to consume a large amount of memory and CPU resources.
23395 Transaction Management 4.3.4 If a Greenplum Database segment failed during two phase transaction processing, the transaction remained in a uncompleted state and was cleaned up only during a Greenplum Database restart. In many cases, this caused high disk consumption by the Greenplum Database xlog process.
23130 Resource Management 4.3.4 Some queries were terminated when they were run with a specific statement_mem value due to a rounding error.
23031 Backup and Restore 4.3.4 When restoring a specific table that was not in the default schema (public) with the gpdbrestore utility from a back up, the table was restored in the public schema.
22526 OS Abstraction 4.3.4 In some cases, Greenplum Database would wait indefinitely for a response from a client application.

This issue has been resolved. See the server configuration parameter gp_connection_send_timeout.

19612 Replication: Segment Mirroring 4.3.4 In some cases, Greenplum Database did not properly handle the transition when segment mirror becomes unavailable. As a result, Greenplum Database becomes unavailable.
18509 Functions and Languages 4.3.4 In some cases, Greenplum Database did not handle data of type date properly and caused a segmentation fault.

4.3.3.x Releases

Table 2. Resolved Issues in 4.3.3.x
Issue Number Category   Description
24677 Backup and Restore 4.3.3.1 In some cases after a successful back up operation, error messages about lock files were incorrectly displayed.

This issue has been resolved.

24667 DDL and Utility Statements 4.3.3.1 When creating a temporary table with the ON COMMIT DELETE ROWS clause in a heavy workload environment, the prepared transaction that created the temporary table failed in some cases.
24641

24508

Monitoring: Commander Center Alerting 4.3.3.1 In the Greenplum Command Center database gpperfmon, performance issues were caused by data skew in the log_alert_history. The distribution key for the table has been changed to resolve the issue. See Changed Features.
24515 Replication: Segment Mirroring 4.3.3.1 In some cases under a heavy workload, logging onto the Greenplum Database segment host as a UNIX user was not possible. This was caused by a Greenplum Database filerep process that was incorrectly sending signals to the user after the process failed to create a sub-process.
23751 Monitoring: gpperfmon server 4.3.3.1 In some cases, a memory leak caused the gpmmon process to consume a large amount of memory and CPU resources.
23395 Transaction Management 4.3.3.1

If a Greenplum Database segment failed during two-phase transaction processing, the transaction remained in a uncompleted state and was cleaned up only during a Greenplum Database restart. In many cases, this caused high disk consumption by the Greenplum Database xlog process.

18509 Functions and Languages 4.3.3.1 In some cases, Greenplum Database did not handle data of type date properly and caused a segmentation fault.
24479 Backup and Restore 4.3.3.0 A table could not be restored (with the gpdbrestore -T option) from a back up that is on a Data Domain Boost system and that was created with the gpcrondump --ddboost options.
24478 Management Scripts: expansion 4.3.3.0 The Greenplum Database gpexpand utility failed when an error table for an external table was present in Greenplum Database. The utility displayed this message:

DETAIL: ALTER TABLE is not allowed on error tables

24326 Query Execution, Storage Access Methods 4.3.3.0 If either a non-partitioned append-only table or an individual append-only part of a partitioned table had more than 127 million rows on a segment, a query that uses an index to access the table data could return duplicate rows.

This issue has been fixed.

24317 Security 4.3.3.0 Greenplum Database software has been updated to use OpenSSL 0.9.8zb in response to the OpenSSL Security Advisory [6 Aug 2014]. For information about the advisory, see https://www.openssl.org/news/secadv_20140806.txt.
24248 GPHDFS 4.3.3.0 The Greenplum Database external table protocol gphdfs supports the Cloudera 4.x and 5.x HDFS distributions. See Hadoop Distribution Compatibility
24237 DDL and Utility Statements 4.3.3.0 Temporary tables were not cleaned up properly in the following situation. A user defined function (UDF) was created with a security definer and that included statements to create the temporary table. The UDF was executed by a regular user who was given EXECUTE permission on the function.

This caused the temporary table to stay in the database after the session was disconnected.

24182 Management Scripts: General 4.3.3.0 Greenplum Database timezone information has been updated to match world-wide timezones. For in formation about timezones, see http://www.iana.org/time-zones.
24168 Vacuum 4.3.3.0 For an append-optimized table that did not contain any data, the VACUUM command did not update the value of relfrozenxid in the catalog table pg_class.
24158 Upgrade / Downgrade 4.3.3.0 When upgrading Greenplum Database from a 4.2.x release to a 4.3.x release prior to 4.3.2.1, append-only tables were not correctly converted to append-optimized tables. In some cases, the incorrect conversion prevented the VACUUM command from reclaiming storage occupied by deleted tuples. For information about the upgrade issue, see Upgrading from 4.3.x to 4.3.3.x.
24119 Query Execution 4.3.3.0 In some cases, a segmentation fault occurred when a DECLARE CURSOR WITH HOLD command was run by an ODBC driver.
24116

21042

Loaders: gpfdist 4.3.3.0 The Greenplum Database gpfdist utility failed with a SIGSEGV error when the utility received a empty request with two consecutive return characters "\n\n".
24089 Loaders: Copy/ExternalTabs 4.3.3.0 Multibyte characters were not handled properly when writing to an external table that uses the gb18030 encoding from a Greenplum database that was created with UTF8 encoding. In some cases, this error was encountered.

ERROR: The size of the value cannot be bigger than the field size value

24079 GPHDFS 4.3.3.0 The Greenplum Database external table protocol gphdfs supports the Pivotal 2.0 distribution.
24068 Postgis 4.3.3.0 When using PostGIS, In some cases a closed curved polygon that was converted to a linear polygon was not closed due to a linear approximation precision issue with PostGIS 2.0.3.
24067 Loaders: gpfdist, Loaders: gpload 4.3.3.0 In some cases when network load was heavy, the Greenplum Database utility gpfdist intermittently failed with this error: gpfdist closed connection to server
24055 Vacuum 4.3.3.0 The VACUUM FULL command transaction processing has been enhanced ensure proper operation with other concurrent operations.
24011 Catalog and Metadata, Vacuum 4.3.3.0 In some cases, when a VACUUM FULL command was cancelled, incorrect handling of Greenplum Database transaction log caused a PANIC signal to be issued and prevented Greenplum Database from performing a crash recovery of a segment mirror.
24001 Backup and Restore 4.3.3.0 During a backup operation, the Greenplum Database utility gpcrondump held an EXCLUSIVE lock on the catalog table pg_class longer than required.
23955 Query Execution 4.3.3.0 In some query plans, where a window operator is under the right child of a nested loops join, wrong results could have been generated because of improper cleanup of the operator's internal state.
23925 Management Scripts: expansion, Management Scripts: General 4.3.3.0 The Greenplum Database utilities gpactivatestandby and gpexpand used SSH to connect to localhost (the Greenplum Database host where the utility was run). Using SSH was redundant as the command was already on the local host and has been eliminated.
23894 Backup and Restore 4.3.3.0 Performing a back up to a Data Domain system failed when the Greenplum Database utility gpcrondump command specified the --ddboost options because gpcrondump performed a disk space check.
23864 Catalog and Metadata 4.3.3.0 Running the REINDEX command on a database while other workloads are concurrently running could create inconsistencies in the database catalog.
23850 Management Scripts 4.3.3.0 In some cases after expanding a Greenplum Database system, running gpinitstandby -n failed to resynchronize the data between the primary and standby master host.
23850 Management Scripts: General 4.3.3.0 In some cases after expanding a Greenplum Database system, running gpinitstandby -n failed to resynchronize the data between the primary and standby master host.
23842 Replication: Segment Mirroring 4.3.3.0 In some rare cases, if a restart occurred while the gprecoverseg utility was running, some tables and a persistent table were detected having less data on a mirror segment that corresponds to a primary segment.
23802 Query Execution 4.3.3.0 Greenplum Database did not manage temporary workfiles (spill files) properly. In some cases, this caused a query that required workfiles to fail with a message that stated that a Greenplum Database segment had reached the maximum configured workfile usage limit.
23753 Backup and Restore 4.3.3.0 The emails sent by the Greenplum Database gpcrondump utility could not be customized. Now the utility supports customized email notification for backup operations.
23730 Backup and Restore, Management Scripts: master mirroring 4.3.3.0 When configuring a Greenplum Database system with a standby master, the gpinitstandby utility did not correctly update the pg_hba.conf file on Greenplum Database segment hosts.
23729 Backup and Restore, DDL and Utility Statements 4.3.3.0 When the -b option was specified with the gpcrondump utility to disable a disk space check, a check was still performed.
23717 Locking, Signals, Processes 4.3.3.0 During Greenplum Database shutdown, a signal-unsafe function call was called from a signal handler function. The signal-unsafe function was replaced.
23699 Monitoring: gpperfmon server 4.3.3.0 Greenplum Database failed when the gpperfmon log files were not encoded in UTF8.

This issue has been resolved.

23637 Backup and Restore 4.3.3.0 When restoring a Greenplum database with the Greenplum Database gpcrondump utility, the utility performed an ANALYZE operation on the entire database. Now the gpcrondump utility analyzes only the restored tables.
23568 Backup and Restore 4.3.3.0 When backing up a Greenplum database with the Greenplum Database gpcrondump utility and specifying an NFS directory with the -u option, the gpcrondump utility created an empty db_dumps directory in the master and segment data directories.
23558 Backup and Restore 4.3.3.0 When restoring a backup from a Data Domain system using --ddboost options, the Greenplum Database gpdbrestore utility failed because it could not find C data and post data files.
23286 Dispatch 4.3.3.0 In some cases, Greenplum Database did not handle the processing of cancelled distributed queries properly.

This issue has been resolved.

22974 Loaders: Copy/ExternalTabs 4.3.3.0 When reading data from external sources, Greenplum Database stopped reading data if the first 1000 rows processed contain formatting errors. Now the limit is configurable.
20504 Query Execution 4.3.3.0 FOR loops in PL/pgSQL did not close the sequence generator if further access was still required.
18562 DDL and Utility Statements 4.3.3.0 A transaction lock did not block reader processes from proceeding when a writer process was holding the same lock. In some cases this caused a race condition to occur.

Now, Greenplum Database blocks reader processes when a writer process holds the same lock to prevent race conditions from occurring.

17264 Replication: Segment Mirroring 4.3.3.0 In some cases, Greenplum Database continuously logged this message when sending file replication process statistics to Greenplum Database perfmon process:

Error when sending file rep stats to perfmon

16450 Backup and Restore 4.3.3.0 When running the Greenplum Database utility pg_dumpall with the option --resource-queues to create scripts that contain resource queue definitions, the utility generated incorrect scripts when the resource queue definition contained the memory_limit option.
16059 Resource Management 4.3.3.0 Some SQL statements that executed a PL/pgSQL function that contained an insert, update, or delete operation did not allocate memory correctly. This caused the following issues:
  • Decreased performance
  • Large number of spill files were created on disk

This issue has been resolved.

4.3.2.x Releases

Table 3. Resolved Issues in 4.3.2.x
Issue Number Category Resolved in Description
24158 Upgrade / Downgrade 4.3.2.1 When upgrading Greenplum Database from a 4.2.x release to a 4.3.x release prior to 4.3.2.1, append-only tables were not correctly converted to append-optimized tables. In some cases, the incorrect conversion prevented the VACUUM command from reclaiming storage occupied by deleted tuples. For information about the upgrade issue, see Product Enhancements.
24326 Query Execution, Storage Access Methods 4.3.2.1 If either a non-partitioned append-only table or an individual append-only part of a partitioned table had more than 127 million rows on a segment, a query that uses an index to access the table data could return duplicate rows.

This issue has been fixed.

24037 Client Access Methods and Tools 4.3.2 In some cases, when the SQLCancel function was used with the Greenplum Database ODBC driver to cancel the execution of a query, a rollback of the transaction did not occur.
23838 Loaders: Copy/External Tables 4.3.2 When the COPY command copied data from a file and the file contained the character sequence '\r\r\n', a postmaster reset occured.
23768 Query Execution 4.3.2 In some cases, the clean up of an aborted transaction was not handled correctly and caused a PANIC signal to be issued.
23751 Monitoring: gpperfmon server 4.3.2 A memory leak caused the gpmmon process to consume a large amount of memory and CPU resources.
23735 Languages: PL/Java 4.3.2 In some cases, Greenplum Database did not handle concurrent shared memory operations properly from PL/Java routines. This caused a PANIC signal to be issued.
23708 Backup and Restore 4.3.2 In some cases, running the Greenplum Database gpdbrestore utility with the -T or --table-file option failed with this error.

ValueError: need more than 1 value to unpack

23706 Upgrade / Downgrade 4.3.2 The Greenplum Database installer did not support upgrading from a Greenplum Database hotfix.
23647 Vacuum 4.3.2 Performing a VACUUM operation on a partitioned append-optimized table did not correctly reduce the age of the parent table and child tables.
23631 Replication: Segment Mirroring 4.3.2 In some rare cases, the crash recovery of a segment mirror failed due to an inconsistent LSN.
23604 Interconnect 4.3.2 In some cases when a Greenplum Database process was cancelled on the Greenplum Database master, corresponding processes remained running on Greenplum Database segment instances.
23578 gphdfs 4.3.2 For Greenplum Database external tables, the gphdfs protocol that accesses data from files on HDFS now supports the CSV file format.
23546 Storage Access Methods 4.3.2 In some cases, a DELETE command that contains a join between an append-optimized table and heap table returned this error:

ERROR: tuple already updated by self

23485 Transaction Management 4.3.2 When a single Greenplum Database session ran transactions, temporary files were not removed after the transaction completed. If a the session ran a large number of transactions, the temporary files required a large amount of disk space.

This issue has been resolved.

23417 Transaction Management 4.3.2 Some queries against an append-optimized table with compression enabled that containd a column with an unknown data type caused a Greenplum Database SIGSEGV error.
23227 Client Access Methods and Tools 4.3.2 For Greenplum Database with GSS Authentication enabled, the database role attribute Valid Until was ignored. The Valid Until parameter is now respected when GSS authentication is enabled.
23222 Client Access Methods and Tools 4.3.2 When Greenplum Database receives a SIGSEGV when running the COPY command, Greenplum Database hangs and continuously log this warning message:

copy: unexpected response (3)

23204 Query Execution 4.3.2 In some cases, when a Greenplum Database segment fault occurred during the execution of a PL/R function, PL/R hung and continuously returned the same error message.
23202 Management Scripts: expansion 4.3.2 During the process of adding new hosts, the Greenplum Database expand utility gpexpand did not update the pg_hba.conf files on Greenplum Database hosts with the correct host information.
23174 Languages: R, PLR 4.3.2 In Greenplum Database, a signal handling issue in the R programming language caused a potential for postgres processes to hang when running PL/R functions.
23138 Replication: Segment Mirroring 4.3.2 The gprecoverseg utility failed to recover a Greenplum Database segment that was marked as down when the data directory location for the segment was a symbolic link, and a postgres process was running with the same PID as the PID associated with the down segment.
23067 Loaders: Copy/External Tables 4.3.2 In some cases, when an INSERT FROM SELECT command was run that selected from readable external able and inserted into writable external table, this warning was generated:

WARNING select failed on curl_multi_fdset (maxfd 10) (4 - Interrupted system call)

23038 Query Execution 4.3.2 When a query was run that contained a polymorphic, user-defined aggregate function, and Greenplum Database was required to create spill files on disk, the query failed with this error.

ERROR: could not determine actual argument type for polymorphic function

This issue has been fixed.

23008 Dispatch 4.3.2 In some cases when temporary tables were used, Greenplum Database did not perform the clean up of temporary namespaces properly after a transaction completed and caused a SIGSEGV.
22914 Loaders: Copy/ExternalTables 4.3.2 When a query joined a heap table with an external table that used the gpfdist protocol, an incorrect plan that returned no results might have been chosen.
22787 Monitoring: gpperfmon server 4.3.2 In some cases, the Greenplum Database gpmmon process failed. The gpmmon process is used for Greenplum Database performance monitoring.
22784 Storage Access Methods 4.3.2 After a database expansion, some tables created with APPENDONLY=TRUE and compression enabled consumed much more disk space than before the expansion.

To reduce disk space in this situation, the Greenplum Database gpreload utility reloads table data with column data sorted.

22706 Management Scripts: master mirroring 4.3.2 The Greenplum Database gpinitstandby utility completed successfully but returned an error when the $GPHOME/share directory was not writable. Now, the utility returns this warning:

Please run gppkg --clean after successful standby initialization.

22592 Backup and Restore 4.3.2 When the Greenplum Database gpdbrestore utility could not find files on the Greenplum Database master segment that are used to perform a restore operation, the utility did not return the correct error message.
22413 Query Planner 4.3.2 In some cases, an SQL query that contains the following returned incorrect results: a combination of a median function with other aggregates where the GROUP BY columns are a subset of the table's distribution columns.
22328 Management Scripts 4.3.2 When a Greenplum Database extension package was updated with the Greenplum Database gppkg utility option -u, gppkg did not warn the user that updating a package includes removing all previous versions of the system objects related to the package.

Now, the gppkg utility warns the user and lets the user cancel the operation.

22265 Locking, Signals, Processes 4.3.2 Greenplum Database hung due to incorrect lock handling that caused a race condition. The lock handling issue was caused by a compiler optimization.
22205 Replication: Segment Mirroring 4.3.2 In some cases, running the Greenplum Database command gprecoverseg -r to rebalance segment instances failed and caused database catalog corruption.
21916 Interconnect 4.3.2 In some cases when the Greenplum Database query dispatcher encountered connection errors, a postmaster reset occured.
21867 DDL and Utility Statements 4.3.2 The performance of Greenplum Database truncate operations degraded between restarts of Greenplum Database.
21103 Query Execution 4.3.2 In Greenplum Database, support of subnormal double-precision (float8) numbers differed between Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. For example, the value 5e-309 was not handled consistently by Greenplum Database on RHEL 5 and RHEL 6. This issue has been resolved.
20600 Query Planner 4.3.2 For some SQL queries that contained a subquery, this error message was returned. ERROR: no parameter found for initplan subquery.
20268 Loaders: Copy/ExternalTables 4.3.2 In some cases when a COPY command was run, improper memory handling caused a PANIC signal to be issued.
19949 Backup and Restore 4.3.2 If a Greenplum database was backed up and the database name contained upper-case characters, the Greenplum Database gpdbrestore utility did not restore the database with the correct name.
19660 Authentication 4.3.2 Greenplum Database supports LDAP authentication. Previously, an issue in Greenplum Database prevented LDAPS (LDAP over SSL) from functioning. This issue has been resolved.
19246 Backup and Restore 4.3.2 When performing a selective restore of a partitioned table from a full backup with the Greenplum Database utility gpdbrestore, the data from leaf partitions are now restored.

Previously, when performing a selective restore of a partitioned table, you needed to specify all the individual leaf partitions.

18774 Loaders 4.3.2 External web tables that use IPv6 addresses no longer require a port number when using the default port.

In previous releases, a port number was required when using an IPv6 address.

13282 Backup and Restore 4.3.2 The database objects in the gp_toolkit schema were not restored after a database was re-created and then restored with the Greenplum Database gpdbrestore utility. The gp_toolkit objects are now restored when a database is re-created and restored.

4.3.1 Release

Table 4. Resolved Issues in 4.3.1
Issue Number Category Resolved in Description
23757 Security 4.3.1 Greenplum Database software has been updated to use OpenSSL 0.9.8za in response to the OpenSSL Security Advisory [05 Jun 2014]. For information about the advisory, see http://www.openssl.org/news/secadv_20140605.txt.
22301 Replication: Master Mirroring 4.3.1 DCA customers who wished to use Greenplum Database 4.3 could not use the utility dca_setup. This issue has been resolved in Greenplum Database 4.3.1.
22281 Backup and Restore 4.3.1 For partitioned append-optimized tables, a partition was backed up even though it was not modified.
21591 Management Scripts Suite 4.3.1 The Greenplum Database utilities gpstart and gprecoverseg hung when checking the process ID in the postmaster.pid file and the ID matched a non-postgres running process.
23421 Locking, Signals, Processes 4.3.1 In some cases, concurrent CREATE TABLE and DROP TABLE operations caused Greenplum Database to hang due to incorrect lock handling.
13825 Functions and Languages, Transaction Management 4.3.1 In PL/PGSQL functions, exception blocks were not handled properly. Depending on where the exception is encountered during function execution, the improper block handling resulted in either the creation of catalog inconsistency between master and segment, or Greenplum Database issuing the following message:

The distributed transaction 'Prepare' broadcast failed to one or more segments.

22655 Locking, Signals, Processes 4.3.1 Greenplum Database hung due to incorrect lock handling that caused a race condition. The lock handling issue was caused by a compiler optimization.
20924 Dispatch 4.3.1 For some queries that contained a window function and that executed on both the master and segments, the query would hang when executed from an ODBC/JDBC client.
21899 Backup and Restore 4.3.1 When performing an incremental backup, the gpcrondump utility backed up temporary tables that existed during the time of the backup. This caused a failure when performing a restore with the gpdbrestore utility that used the incremental backup.
22293 Backup and Restore 4.3.1 Greenplum Database supports Data Domain DDOS 5.4. See Supported Platforms for information about supported versions of Data Domain Boost.
22442 Loaders: gpfdist 4.3.1 The Greenplum Database Load Tools for Windows installation did not include the gssapi and auth libraries. This issue has been resolved.
19476 Client Access Methods and Tools 4.3.1 Running multiple gpload sessions simultaneously that loaded data into the same table resulted in inconsistent data in the table. See the gpload information in Product Enhancements.
22863 DDL and Utility Statements 4.3.1 When > (greater than) was used in the CREATE OPERATOR CLASS command as an operator name, this error was returned.

operator > is not a valid ordering operator when using operator classes

22219 Query Planner 4.3.1 In certain queries that contain the median function and a GROUP BY clause, the query planner produced an incorrect plan in which some necessary columns were not projected in the operator nodes. This caused an error when trying to look up the missing columns.
22084 OS Abstraction 4.3.1 Improved handing of situations where Greenplum Database encounters segment violation errors.
17995 DDL and Utility Statements 4.3.1 In some cases, the functions pg_cancel_backend() and pg_terminate_backend() did not terminate sessions.
17773 DDL and Utility Statements 4.3.1 Greenplum Database did not properly check privileges during certain RESET ALL operations.
17481 Catalog and Metadata, DDL and Utility Statements 4.3.1 Queries on the system view pg_partitions could fail to return when DDL statements on partitioned tables were running concurrently.
15834 Loaders: Copy/ExternalTabs 4.3.1 A COPY command cancel request (Ctrl+c) followed by another COPY command and a cancel request caused the Greenplum Database session to hang. When cancel request was attempted again, a SIGSEGV error occured.
14367 DDL and Utility Statements 4.3.1 ALTER TABLE ADD COLUMN with default NULL was not supported for append-optimized tables. This syntax is now supported.
21522 Backup and Restore 4.3 The Greenplum Database utility pg_dump printed information-level messages (messages with the label [INFO]) to stderr that were not printed in previous releases. These messages were printed even when pg_dump completes without errors.

4.3 Release

Table 5. Resolved Issues in 4.3
Issue Number Category Description
21522 Backup and Restore The Greenplum Database utility pg_dump printed information-level messages (messages with the label [INFO]) to stderr that were not printed in previous releases. These messages were printed even when pg_dump completes without errors.