Greenplum Database coordinator logs show the following notice:
NOTICE,""Operator ??????????????????????????????????? not supported"",
It looks as if the NOTICE logging is failing to input more information as to why the Operator is not supported.
We have found that the Orca Optimizer encountered an unexpected operator (which shouldn't occur) and fall back to the Planner. However when falling back, the error message is improperly set as a char instead of wchar, and this results in undefined text being output.
The fix will be available in Greenplum Database version 7.6.0