null return value of null should not be confused with a SQL NULL. While calling json_typeof('null'::json) will return null, calling json_typeof(NULL::json) will return a SQL NULL. 796 f1 f2 797 1 true null return value of null should not be confused with a SQL NULL. While calling json_typeof('null'::json) will return null, calling json_typeof(NULL::json) will return a SQL NULL. 1704 f1 f2 1704 1 true 12690 Resolves an issue where, when a memory limit was hit, a query was throwing errors without calling the correct cleanup function. 13874 Resolves an error handling issue that caused PANIC errors during

null return value of null should not be confused with a SQL NULL. While calling json_typeof('null'::json) will return null, calling json_typeof(NULL::json) will return a SQL NULL. 689 f1 f2 690 1 true null return value of null should not be confused with a SQL NULL. While calling json_typeof('null'::json) will return null, calling json_typeof(NULL::json) will return a SQL NULL. 1501 f1 f2 1502 1 true 12690 Resolves an issue where, when a memory limit was hit, a query was throwing errors without calling the correct cleanup function. 13874 Resolves an error handling issue that caused PANIC errors during

12690 : Resolves an issue where, when a memory limit was hit, a query was throwing errors without calling the correct cleanup function. 13874 : Resolves an error handling issue that caused PANIC errors corruption could occur when an invalid snapshot was used with an AO table. Resolves an issue where calling the gpmt utility with the primarymirror_lengths option was failing due to unavailability of the Queries have been updated to use the gp_segment_configuration table instead. Resolves an issue where calling the gpmt utility with the tablecollect option was failing because the pg_class table no longer has

12690 Resolves an issue where, when a memory limit was hit, a query was throwing errors without calling the correct cleanup function. 13874 Resolves an error handling issue that caused PANIC errors during used with VMware Greenplum 6 Documentation VMware, Inc 165 an AO table. Resolves an issue where calling the gpmt utility with the primarymirror_lengths option was failing due to unavailability of the Queries have been updated to use the gp_segment_configuration table instead. Resolves an issue where calling the gpmt utility with the tablecollect option was failing because the pg_class table no longer has

12690 : Resolves an issue where, when a memory limit was hit, a query was throwing errors without calling the correct cleanup function. 13874 : Resolves an error handling issue that caused PANIC errors corruption could occur when an invalid snapshot was used with an AO table. Resolves an issue where calling the gpmt utility with the primarymirror_lengths option was failing due to unavailability of the Queries have been updated to use the gp_segment_configuration table instead. Resolves an issue where calling the gpmt utility with the tablecollect option was failing because the pg_class table no longer has

12690 : Resolves an issue where, when a memory limit was hit, a query was throwing errors without calling the correct cleanup function. 13874 : Resolves an error handling issue that caused PANIC errors corruption could occur when an invalid snapshot was used with an AO table. Resolves an issue where calling the gpmt utility with the primarymirror_lengths option was failing due to unavailability of the Queries have been updated to use the gp_segment_configuration table instead. Resolves an issue where calling the gpmt utility with the tablecollect option was failing because the pg_class table no longer has

whether those primaries needed to be updated. 31350 : Resolved an issue where gpmovemirrors -B was calling gprecoverseg with an excessively large number of parallel processes. 31338, 31351 : Resolved an - gpinitsystem : gpinitsystem now exports the MASTER_DATA_DIRECTORY environment variable before calling gpconfig, to avoid throwing warning messages when configuring system parameters on Greenplum Database hosts). The Greenplum Database host naming convention for the master host is mdw and for the standby master host is smdw. The segment host naming convention is sdwN where sdw is a prefix and N is an integer

whether those primaries needed to be updated. 31350 : Resolved an issue where gpmovemirrors -B was calling gprecoverseg with an excessively large number of parallel processes. 31338, 31351 : Resolved an - gpinitsystem : gpinitsystem now exports the MASTER_DATA_DIRECTORY environment variable before calling gpconfig, to avoid throwing warning messages when configuring system parameters on Greenplum Database hosts). The Greenplum Database host naming convention for the master host is mdw and for the standby master host is smdw. The segment host naming convention is sdwN where sdw is a prefix and N is an integer

The Greenplum Database host naming convention for the coordinator host is cdw and for the standby coordinator host is scdw. The segment host naming convention is sdwN where sdw is a prefix and N is is recommended for hosts with multiple interfaces, but when the interfaces are not bonded, the convention is to append a dash (-) and number to the host name. For example, sdw1-1 and sdw1-2 are the two account on each node to run and administer Greenplum Database. This user account is named gpadmin by convention. The gpadmin user must have permission to access the services and directories required to install

corruption could occur when an invalid snapshot was used with an AO table. Resolves an issue where calling the gpmt utility with the primarymirror_lengths option was failing due to unavailability of the Queries have been updated to use the gp_segment_configuration table instead. Resolves an issue where calling the gpmt utility with the tablecollect option was failing because the pg_class table no longer has whether those primaries needed to be updated. 31350 : Resolved an issue where gpmovemirrors -B was calling gprecoverseg with an excessively large number of parallel processes. 31338, 31351 : Resolved an