anyelement, from_json jsonb) anyelement Expands the object in from_json to a row whose columns match the record type defined by base. See the Notes. select * from json_populate_record(null::myrowtype setof anyelement Expands the outermost array of objects in from_json to a set of rows whose columns match the record type defined by base. See the Notes. select * from json_populate_recordset(null::myrowtype jsonb_path_exists(‘{“a”:[1,2,3,4,5]}’, ‘$.a[*] ? (@ >= $min && @ <= $max)’, ‘{“min”:2,“max”:4}’) true jsonb_path_match(target jsonb, path jsonpath [, vars jsonb [, silent bool]]) boolean Returns the result of JSON path

e anyelement, from_json jsonb) anyelement Expands the object in from_json to a row whose columns match the record type defined by base. See Note 1. select * from json_populate_record(null::myrowtype, ‘{“a”:1 setof anyelement Expands the outermost array of objects in from_json to a set of rows whose columns match the record type defined by base. See Note 1. select * from json_populate_recordset(null::myrowtype not appear in the target row type will be omitted from the output, and target columns that do not match any JSON field will be NULL. The json_typeof function null return value of null should not be confused

e anyelement, from_json jsonb) anyelement Expands the object in from_json to a row whose columns match the record type defined by base. See Note 1. select * from json_populate_record(null::myrowtype, ‘{“a”:1 setof anyelement Expands the outermost array of objects in from_json to a set of rows whose columns match the record type defined by base. See Note 1. select * from json_populate_recordset(null::myrowtype not appear in the target row type will be omitted from the output, and target columns that do not match any JSON field will be NULL. The json_typeof function null return value of null should not be confused

key(s) for the staging table. If the target table was created DISTRIBUTED RANDOMLY, gpload uses the MATCH_COLUMNS as the staging table’s distribution key(s). 181229489 Resolves an issue where gpload did with the text provided user name () and authenticated user name () do not match because it performed an unnecessary authentication check. 12647 Synchronizes the Greenplum Database occurred because the query optimizer did not add scalar casts for any input columns whose types did not match the output types of the SetOp. Release 6.16.0 Release Date: 2021-4-22 VMware Tanzu Greenplum 6

key(s) for the staging table. If the target table was created DISTRIBUTED RANDOMLY, gpload uses the MATCH_COLUMNS as the staging table's distribution key(s). 181229489 : Resolves an issue where gpload did with the text provided user name () and authenticated user name () do not match because it performed an unnecessary authentication check. 12647 Synchronizes the Greenplum Database occurred because the query optimizer did not add scalar casts for any input columns whose types did not match the output types of the SetOp. Release 6.16.0 Release Date: 2021-4-22 VMware Tanzu Greenplum 6

column was not present in the staging table. This issue is resolved. gpload now attempts to use the match columns as the distribution key of the staging table, or provides no distribution clause at all. key(s) for the staging table. If the target table was created DISTRIBUTED RANDOMLY, gpload uses the MATCH_COLUMNS as the staging table's distribution key(s). 181229489 : Resolves an issue where gpload did with the text provided user name () and authenticated user name () do not match because it performed an unnecessary authentication check. 12647 Synchronizes the Greenplum Database

column was not present in the staging table. This issue is resolved. gpload now attempts to use the match columns as the distribution key of the staging table, or provides no distribution clause at all. key(s) for the staging table. If the target table was created DISTRIBUTED RANDOMLY, gpload uses the MATCH_COLUMNS as the staging table's distribution key(s). 181229489 : Resolves an issue where gpload did with the text provided user name () and authenticated user name () do not match because it performed an unnecessary authentication check. 12647 Synchronizes the Greenplum Database

Functions. These Greenplum Database extensions are installed with Greenplum Database Fuzzy String Match Extension PL/Python Extension pgcrypto Extension Data Connectors Greenplum Platform Extension redistributing a Left Outer Join. This issue has been addressed by allowing the join inner child to match the distribution of the outer child via a redistribution motion. Server 31888 : Resolved an issue occurred because the query optimizer did not add scalar casts for any input columns whose types did not match the output types of the SetOp. Release 6.16.0 Release Date: 2021-4-22 VMware Greenplum v6.18 Documentation

Functions. These Greenplum Database extensions are installed with Greenplum Database Fuzzy String Match Extension PL/Python Extension pgcrypto Extension Data Connectors Greenplum Platform Extension with the text provided user name () and authenticated user name () do not match because it performed an unnecessary authentication check. 12647 : Synchronizes the Greenplum Database occurred because the query optimizer did not add scalar casts for any input columns whose types did not match the output types of the SetOp. Release 6.16.0 Release Date: 2021-4-22 VMware Greenplum v6.19 Documentation

Functions. These Greenplum Database extensions are installed with Greenplum Database Fuzzy String Match Extension PL/Python Extension pgcrypto Extension Data Connectors Greenplum Platform Extension second information, Greenplum Database cannot match the system timezone with a PostgreSQL timezone. In this case, Greenplum Database calculates a "best match" with a PostgreSQL timezone based on information Greenplum Database master and segment instances, and prevents Greenplum Database from selecting a best match timezone each time the cluster is restarted, using the current system timezone and Greenplum Database