System information

Resolved Issues in Greenplum Database 4.2.7.3 3
Greenplum Database 4.2.7.3 Release Notes
Resolved Issues in Greenplum Database 4.2.7.3
The table below lists issues that are now resolved in Greenplum Database 4.2.7.3. For
issues resolved in prior releases, refer to the corresponding release notes available
from
Support Zone.
Table 1 Resolved Issues in 4.2.7.3
Issue
Number
Category
Resolved
in
Description
22787 Monitoring:
gpperfmon
server
4.2.7.3 In some cases, the Greenplum Database gpmmon process failed. The
gpmmon process is used for Greenplum Database performance
monitoring.
22572 Loaders:
Copy/External
Tables
4.2.7.2 In some cases, SQL queries intermittently failed when reading from
external web tables and the web table was serving data over HTTP
from a traditional web server.
22442 Loaders:
gpfdist
4.2.7.2 The Greenplum Database Load Tools for Windows installation did not
include the gssapi and auth libraries. This issue has been resolved.
22317 Loaders:
gpfdist
4.2.7.2 When the Greenplum Database gpfdist utility was used with a named
pipe for a readable external table, and there was no data from the pipe
for more than 10 minutes, gpfdist failed.
22293 Backup and
Restore
4.2.7.2 Greenplum Database supports Data Domain DDOS 5.4. See
Supported Platforms for information about supported versions of Data
Domain Boost.
22219
20076
Query Planner 4.2.7.2 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.
22266 Parser 4.2.7.1 When processing an SQL query, it was incorrectly assumed that the
data type for DISTINCT columns in a subquery took the outer query
data type when the outer query was part of a UNION. These types of
queries might have returned an error.
22254 Monitoring:
gpperfmon
server
4.2.7.1 In some cases, Greenplum Command Center displayed incorrect CPU
system information in the System Metrics tab.
22210 Backup and
Restore
4.2.7.1 When restoring sets of tables with the Greenplum Database
gpdbrestore utility, primary keys, indexes, and GRANT privileges were
not restored for filtered tables.
For tables with non-English characters (for example, table name and
records contained Korean or Chinese characters) primary keys,
indexes and GRANT privileges were not restored.
For tables with English characters, GRANT privileges were not
restored.
22077 Transaction
Management
4.2.7.1 A Greenplum Database internal function caused a buffer overrun when
a combination of the following information created a very long string:
user name, database name, and client host information.
22072 Backup and
Restore
4.2.7.1 An incremental backup created with gpcrondump did not generate the
correct restore list if some tables were dropped after an ACCESS
SHARED lock was released. Moved the lock on pg_class to the
gpcrondump utility from the gp_dump utility for better consistency.