System information

Known Issues in Greenplum Database 4.2.7.3 7
Greenplum Database 4.2.7.3 Release Notes
Known Issues in Greenplum Database 4.2.7.3
This section lists the known issues in Greenplum Database 4.2.7.3. A workaround is
provided where applicable.
For known issues discovered in previous releases, including patch releases to
Greenplum Database 4.1 or 4.0.x, see the corresponding release notes, available from
Support Zone:
Table 2 All Known Issues in 4.2.7.3
Issue Category Description
22413 Query Planner In some cases, an SQL query that contains the following returns 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.
The planner does not correctly redistribute the data to ensure proper
collocation of the join tuples, and as a result the join produces incorrect
results.
22560 Catalog and
Metadata
In PL/pgSQL user-defined functions, exceptions are not handled properly. If
the function contains exception blocks, the function should not issue DDL
commands, TRUNCATE commands, or inserts into append-only
column-oriented tables.
22442 Loaders: gpfdist The Greenplum Database Load Tools for Windows is missing gssapi and auth
libraries.
Workaround: Install the Greenplum Database Client Tools for Windows. The Client
Tools include the missing libraries. The Load Tools will use the libraries from the
Client Tools.
22172 DDL and Utility
Statements
OLAP queries with a HAVING clause that filters for NULL on dimension
columns incorrectly return empty results.
20453 Query Planner For SQL queries of either of the following forms:
SELECT columns FROM table WHERE table.column NOT IN subquery;
SELECT columns FROM table WHERE table.column = ALL subquery;
tuples that satisfy both of the following conditions are not included in the
result set:
• table.column is NULL.
• subquery returns the empty result.
21724 Query Planner 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 generates zero
tuples and directly contributes to the output of the second stage plan,
incorrect results might be returned.
21838 Backup and
Restore
When restoring sets of tables with the Greenplum Database utility
gpdbrestore, the table schemas must be defined in the database. If a table’s
schema is not defined in the database, the table is not restored. When
performing a full restore, the database schemas are created when the tables
are restored.
Workaround: Before restoring a set of tables, create the schemas for the tables in
the database.
21129 DDL and Utility
Statements
SSL is only supported on the master host. It is not supported on segment
hosts.