generating a PANIC when running certain queries. 12703 : Greenplum was generating a PANIC due to a null pointer reference when creating an extension. This has been fixed by resetting the related global variables excessive external bandwith due to misuse of the hostname and address in gp_segment_configuration. Greenplum Database now uses the primary’s address for WAL-replication in gpexpand. 11371 : Greenplum Database where Greenplum processes crashed when trying to write an error message to the log due to a null pointer dereference. 167242211 : Resolved an issue that caused wrong results when running queries with GPORCA

gp_command_count 1901 gp_connection_send_timeout 1902 gp_content 1902 gp_count_host_segments_using_address 1902 gp_create_table_random_default_distribution 1902 gp_dbid 1903 gp_debug_linger 1903 gp_d gp_ignore_error_table 1915 gp_initial_bad_row_limit 1916 gp_instrument_shmem_size 1916 gp_interconnect_address_type 1916 gp_interconnect_cursor_ic_table_size 1917 gp_interconnect_debug_retry_interval 1917 Greenplum Database 6.26.0 introduces the upgrade_check.py utility, which helps you identify and address the main challenges associated with an in-place upgrade from EL 7 to 8. See Migrating VMware Greenplum

gp_command_count 1861 gp_connection_send_timeout 1861 gp_content 1861 gp_count_host_segments_using_address 1861 gp_create_table_random_default_distribution 1862 gp_dbid 1863 gp_debug_linger 1863 gp_d gp_ignore_error_table 1874 gp_initial_bad_row_limit 1875 gp_instrument_shmem_size 1875 gp_interconnect_address_type 1875 gp_interconnect_debug_retry_interval 1876 gp_interconnect_fc_method 1876 gp_interco gpmmon process to make sure gpdb_get_master_data_dirsets themaster_data_dir` variable to a non-null pointer. 15856 Resolves an issue where the minirepo utility was ignoring table sequences. 15854 VMware

excessive external bandwith due to misuse of the hostname and address in gp_segment_configuration. Greenplum Database now uses the primary’s address for WAL-replication in gpexpand. 11371 : Greenplum Database where Greenplum processes crashed when trying to write an error message to the log due to a null pointer dereference. 167242211 : Resolved an issue that caused wrong results when running queries with GPORCA resolves these issues: Query Optimizer 31715 : A memory allocation function failed to handle a null pointer exception, which could lead to a system panic when creating the memory pools on Greenplum segments

gp_command_count 1867 gp_connection_send_timeout 1867 gp_content 1868 gp_count_host_segments_using_address 1868 gp_create_table_random_default_distribution 1868 gp_dbid 1869 gp_debug_linger 1869 gp_d gp_ignore_error_table 1880 gp_initial_bad_row_limit 1881 gp_instrument_shmem_size 1881 gp_interconnect_address_type 1881 gp_interconnect_debug_retry_interval 1882 gp_interconnect_fc_method 1882 gp_interco Resolved Issues Server 32596 Resolved an issue where Greenplum Database dereferenced a null pointer and PANICed during execution of a query that included record-type parameters. 32567 Resolved an

gp_ignore_error_table 1820 gp_initial_bad_row_limit 1820 gp_instrument_shmem_size 1820 gp_interconnect_address_type 1821 gp_interconnect_debug_retry_interval 1821 gp_interconnect_fc_method 1821 gp_interco Resolved Issues Server 32596 Resolved an issue where Greenplum Database dereferenced a null pointer and PANICed during execution of a query that included record-type parameters. 32567 Resolved an Inc 140 package versions for lxml, nltk, tenserflow, tenserflow-gpu, and keras were updated to address CVEs. pg_dump performance was improved to reduce the time required to dump database schemas during

excessive external bandwith due to misuse of the hostname and address in gp_segment_configuration. Greenplum Database now uses the primary’s address for WAL-replication in gpexpand. 11371 : Greenplum Database where Greenplum processes crashed when trying to write an error message to the log due to a null pointer dereference. 167242211 : Resolved an issue that caused wrong results when running queries with GPORCA resolves these issues: Query Optimizer 31715 : A memory allocation function failed to handle a null pointer exception, which could lead to a system panic when creating the memory pools on Greenplum segments

gp_ignore_error_table 1812 gp_initial_bad_row_limit 1812 gp_instrument_shmem_size 1813 gp_interconnect_address_type 1813 gp_interconnect_debug_retry_interval 1814 gp_interconnect_fc_method 1814 gp_interco package. The package versions for lxml, nltk, tenserflow, tenserflow-gpu, and keras were updated to address CVEs. pg_dump performance was improved to reduce the time required to dump database schemas during Postgres Planner when this parameter is set to off. Data Flow 13811, 8194 : Removes unnecessary null pointer checks in gpcloud. 13882 : Replaces escape characters with spaces in s3 protocol URLs to prevent

gp_ignore_error_table 1600 gp_initial_bad_row_limit 1600 gp_instrument_shmem_size 1601 gp_interconnect_address_type 1601 gp_interconnect_debug_retry_interval 1601 gp_interconnect_fc_method 1601 gp_interco Greenplum Database now includes a configuration parameter — gp_interconnect_address_type — to specify the type of address binding strategy Greenplum Database uses for communication between segment host users, if their configuration permits, to specify that Greenplum use a unicast address — rather than a wildcard address — for interconnect sockets. This reduces port usage on segment hosts and prevents

resolves these issues: Query Optimizer 31715 A memory allocation function failed to handle a null pointer exception, which could lead to a system panic when creating the memory pools on Greenplum segments external table that uses the gpfdists protocol fails if the external table does not use an IP address when specifying a host system in the LOCATION clause of the external table definition. n/a Materialized evenly balanced over the number of available interfaces. This is done by creating separate host address names for each network interface. For example, if a host has four network interfaces, then it would