issue where an INSERT command was terminated by a signal11: Segmentation fault error. 33074 The message canceling statement due to user request now provides the duration time of the failed query in order hung indefinitely. 16553 Resolves an issue where the ic-proxy process did not provide an error message when the peer listener failed. It now displays the error ERROR: SetupInterconnect: We are in IC_PROXY issue generated a PANIC with the error ERRORDATA_STACK_SIZE exceeded. This fix prints an error message with write_stderr instead when encountering the same scenario. 16299 Resolves a bug that caused

issue generated a PANIC with the error ERRORDATA_STACK_SIZE exceeded. This fix prints an error message with write_stderr instead when encountering the same scenario. 16299 Resolves a bug that caused temporary tables when running analyzedb. 16209 Modifies the warning level from ERROR to NOTICE of a message that reports that parameterized queries are not supported. 16176 Adds support for indexscan plans several issues. Server 32932, 32968 Resolves an issue where queries were failing with the error message, ERROR: could not find hash function for hash operator. 16005 Resolves an issue where queries

to archive a file that had already been archived. N/A Changes the level of an autovacuum log message from LOG to DEBUG1. 30755, 32491 Resolves an issue where pg_dump failed with error unsupported execution in entrydb query execution that reported incorrect number of rows. 15087 Includes an error message when setting statement_mem to a value greater than max_statement_mem. 15152 Enhances logging for Greenplum 6 Documentation VMware, Inc 139 distribution policy. 13964 Changed an Assert to a FATAL message log to avoid a crash. 13722 Resolved several assertion failures that could occur for queries with

init_table_size_table() function, a single error message is logged when the Greenplum cluster starts up. In earlier versions of diskquota, the error message was logged repeatedly (approximately every 2 seconds) preferred roles. gpexpand now correctly assigns port numbers in this case, but generates a warning message to indicate that segments are not operating in their preferred roles. DataDirect ODBC 32225 The failing the primary over prematurely. 32140 Resolves an issue where queries were failing with the message “bind: Address already in use”. This was due to Greenplum Database running out of UDP ephemeral

init_table_size_table() function, a single error message is logged when the Greenplum cluster starts up. In earlier versions of diskquota, the error message was logged repeatedly (approximately every 2 seconds) preferred roles. gpexpand now correctly assigns port numbers in this case, but generates a warning message to indicate that segments are not operating in their preferred roles. DataDirect ODBC 32225 The failing the primary over prematurely. 32140 : Resolves an issue where queries were failing with the message “bind: Address already in use”. This was due to Greenplum Database running out of UDP ephemeral

failing the primary over prematurely. 32140 Resolves an issue where queries were failing with the message “bind: Address already in use”. This was due to Greenplum Database running out of UDP ephemeral use the current default storage options. 13920 Removes platform-specific limitation from socket message type recognition logic by using int. 13212 Resolves an issue where the Postgres Planner returned Cluster Management 32018 Resolves an issue where running gpstate -e on the master generated the message FATAL","57P03","connections to primary segments are not allowed. Query Optimizer 32126 Resolves

memory leak that was introduced with the fix for issue 31740. 13040 : Clarifies a misleading error message that was displayed when resource group-based resource managment was active and Greenplum Database configuration parameter. 12851 : Resolves an issue where Greenplum Database logged an INFO-level message with the text provided user name () and authenticated user name () do not in the backend. 10955 : Improved the logging and adjusted log level from INFO to DEBUG for the message We thought we were done (...) but libpq says we are still busy. 179498672 : When using mirrorless

gprecoverseg utility now includes error handling for a mirrorless configuration by displaying the message GPDB Mirroring replication is not configured for this Greenplum Database instance. 178978375 : temp_tablespaces. 31617 - Resource Groups : A database instance was failing to start up, with the message Command pg_ctl reports Master gdm instance active because a mirror segment couldn’t be recovered 179244161 : Resolved an issue where Greenplum processes crashed when trying to write an error message to the log due to a null pointer dereference. 167242211 : Resolved an issue that caused wrong results

use the current default storage options. 13920 : Removes platform-specific limitation from socket message type recognition logic by using int. 13212 : Resolves an issue where the Postgres Planner returned VMware, Inc. 143 32018 : Resolves an issue where running gpstate -e on the master generated the message FATAL","57P03","connections to primary segments are not allowed. Query Optimizer 32126 : Resolves Inc. 146 32038 : Resolves an issue where SELECT * from was intermittently failing with the message “FATAL: Internal error: Using fd > 65535 in MPP_FD_SET”. 32089 : Resolves an issue where the server

not just locked it), then Greenplum Database rolls back the REPEATABLE READ transaction with the message: ERROR: could not serialize access due to concurrent update because a REPEATABLE READ transaction transactions after the REPEATABLE READ transaction began. When an application receives this error message, it should abort the current transaction and retry the whole transaction from the beginning. The Greenplum Database stops accepting transactions to prevent assigning an XID value twice and issues this message. FATAL: database is not accepting commands to avoid wraparound data loss in data base ""