1735 gp_interconnect_address_type 1736 gp_interconnect_debug_retry_interval 1736 gp_interconnect_fc_method 1736 gp_interconnect_proxy_addresses 1737 gp_interconnect_queue_depth 1738 gp_interconnect_setup_timeout covering indexes allow you to add additional columns to an index using the INCLUDE clause, in order to make the use of index-only scans more effective. See Understanding Index-Only Scans and Covering Indexes The new option INDEX_CLEANUP allows VACUUM to skip index cleanup. Setting the option to false will make VACUUM run as quickly as possible, for example, to avoid imminent transaction ID wraparound. VACUUM

gp_interconnect_cursor_ic_table_size 1917 gp_interconnect_debug_retry_interval 1917 gp_interconnect_fc_method 1917 gp_interconnect_proxy_addresses 1918 gp_interconnect_queue_depth 1918 gp_interconnect_setup_timeout because a variable was not found where expected. 15963 Introduces a new check for gpmmon process to make sure gpdb_get_master_data_dirsets themaster_data_dir` variable to a non-null pointer. 15856 Resolves root table, which can be expensive. The problem was resolved by advancing the command counter to make the page and tuple updates visible when merging the leaf statistics. 31774 Resolves an issue where

1881 gp_interconnect_address_type 1881 gp_interconnect_debug_retry_interval 1882 gp_interconnect_fc_method 1882 gp_interconnect_proxy_addresses 1882 gp_interconnect_queue_depth 1883 gp_interconnect_setup_timeout root table, which can be expensive. The problem was resolved by advancing the command counter to make the page and tuple updates visible when merging the leaf statistics. 31774 Resolves an issue where which are not found in standard PostgreSQL. Many features and optimizations developed by Greenplum make their way into the PostgreSQL community. For example, table partitioning is a feature first developed

1875 gp_interconnect_address_type 1875 gp_interconnect_debug_retry_interval 1876 gp_interconnect_fc_method 1876 gp_interconnect_proxy_addresses 1876 gp_interconnect_queue_depth 1877 gp_interconnect_setup_timeout because a variable was not found where expected. 15963 Introduces a new check for gpmmon process to make sure gpdb_get_master_data_dirsets themaster_data_dir` variable to a non-null pointer. 15856 Resolves root table, which can be expensive. The problem was resolved by advancing the command counter to make the page and tuple updates visible when merging the leaf statistics. 31774 Resolves an issue where

1820 gp_interconnect_address_type 1821 gp_interconnect_debug_retry_interval 1821 gp_interconnect_fc_method 1821 gp_interconnect_proxy_addresses 1822 gp_interconnect_queue_depth 1822 gp_interconnect_setup_timeout root table, which can be expensive. The problem was resolved by advancing the command counter to make the page and tuple updates visible when merging the leaf statistics. 31774 Resolves an issue where which are not found in standard PostgreSQL. Many features and optimizations developed by Greenplum make their way into the PostgreSQL community. For example, table partitioning is a feature first developed

1813 gp_interconnect_address_type 1813 gp_interconnect_debug_retry_interval 1814 gp_interconnect_fc_method 1814 gp_interconnect_proxy_addresses 1814 gp_interconnect_queue_depth 1815 gp_interconnect_setup_timeout root table, which can be expensive. The problem was resolved by advancing the command counter to make the page and tuple updates visible when merging the leaf statistics. 31774 Resolves an issue where which are not found in standard PostgreSQL. Many features and optimizations developed by Greenplum make their way into the PostgreSQL community. For example, table partitioning is a feature first developed

1601 gp_interconnect_address_type 1601 gp_interconnect_debug_retry_interval 1601 gp_interconnect_fc_method 1601 gp_interconnect_proxy_addresses 1602 gp_interconnect_queue_depth 1602 gp_interconnect_setup_timeout root table, which can be expensive. The problem was resolved by advancing the command counter to make the page and tuple updates visible when merging the leaf statistics. 31774 Resolves an issue where which are not found in standard PostgreSQL. Many features and optimizations developed by Greenplum make their way into the PostgreSQL community. For example, table partitioning is a feature first developed

it 1609 gp_instrument_shmem_size 1609 gp_interconnect_debug_retry_interval 1609 gp_interconnect_fc_method 1610 gp_interconnect_proxy_addresses 1610 gp_interconnect_queue_depth 1611 gp_interconnect_setup_timeout root table, which can be expensive. The problem was resolved by advancing the command counter to make the page and tuple updates visible when merging the leaf statistics. 31774 : Resolves an issue where environment for Greenplum Database software installation. Perform the following tasks in order: 1. Make sure your host systems meet the requirements described in Platform Requirements. 2. Disable or configure

it 1586 gp_instrument_shmem_size 1586 gp_interconnect_debug_retry_interval 1587 gp_interconnect_fc_method 1587 gp_interconnect_proxy_addresses 1587 gp_interconnect_queue_depth 1588 gp_interconnect_setup_timeout root table, which can be expensive. The problem was resolved by advancing the command counter to make the page and tuple updates visible when merging the leaf statistics. 31774 : Resolves an issue where environment for Greenplum Database software installation. Perform the following tasks in order: 1. Make sure your host systems meet the requirements described in Platform Requirements. 2. Disable or configure

it 1597 gp_instrument_shmem_size 1597 gp_interconnect_debug_retry_interval 1597 gp_interconnect_fc_method 1598 gp_interconnect_proxy_addresses 1598 gp_interconnect_queue_depth 1599 gp_interconnect_setup_timeout root table, which can be expensive. The problem was resolved by advancing the command counter to make the page and tuple updates visible when merging the leaf statistics. 31774 : Resolves an issue where environment for Greenplum Database software installation. Perform the following tasks in order: 1. Make sure your host systems meet the requirements described in Platform Requirements. 2. Disable or configure