distribution utility includes these SSL-related features and changes: A new option named --ssl_verify_peer that you can specify to enable or disable gpfdist SSL certificate authentication. When verify_gpfdists_cert server configuration parameter (default value true) and the gpfdist --ssl_verify_peer option (default value on) control whether SSL certificate authentication is enabled when authorities, root.crt The certificate files required for each verify_gpfdists_cert and --ssl_verify_peer setting combination are identified in the table below: Note A server started with the gpfdist --ssl

indefinitely. 16553 Resolves an issue where the ic-proxy process did not provide an error message when the peer listener failed. It now displays the error ERROR: SetupInterconnect: We are in IC_PROXY mode, but might drop packets and generate interconnect errors due to incorrect cache eviction logic on remote peer shutdown. 32367 Resolved an issue where Greenplum Database was consuming high amounts of memory teardown operations. A timeout mechanism was introduced to ensure that sender(s) have closed the peer end of the receiver's connections. 32314-2 Resolved a problem where logs from ic_proxy did not

might drop packets and generate interconnect errors due to incorrect cache eviction logic on remote peer shutdown. 32367 Resolved an issue where Greenplum Database was consuming high amounts of memory teardown operations. A timeout mechanism was introduced to ensure that sender(s) have closed the peer end of the receiver’s connections. 32314-2 Resolved a problem where logs from ic_proxy did not ROW; it sets the frame to be all rows from the partition start up through the current row’s last peer (a row that ORDER BY considers equivalent to the current row, or all rows if there is no ORDER BY)

might drop packets and generate interconnect errors due to incorrect cache eviction logic on remote peer shutdown. 32367 Resolved an issue where Greenplum Database was consuming high amounts of memory teardown operations. A timeout mechanism was introduced to ensure that sender(s) have closed the peer end of the receiver’s connections. 32314-2 Resolved a problem where logs from ic_proxy did not ROW; it sets the frame to be all rows from the partition start up through the current row’s last peer (a row that ORDER BY considers equivalent to the current row, or all rows if there is no ORDER BY)

might drop packets and generate interconnect errors due to incorrect cache eviction logic on remote peer shutdown. 32367 Resolved an issue where Greenplum Database was consuming high amounts of memory teardown operations. A timeout mechanism was introduced to ensure that sender(s) have closed the peer end of the receiver's connections. 32314-2 Resolved a problem where logs from ic_proxy did not ROW; it sets the frame to be all rows from the partition start up through the current row's last peer (a row that ORDER BY considers equivalent to the current row, or all rows if there is no ORDER BY)

might drop packets and generate interconnect errors due to incorrect cache eviction logic on remote peer shutdown. 32367 Resolved an issue where Greenplum Database was consuming high amounts of memory teardown operations. A timeout mechanism was introduced to ensure that sender(s) have closed the peer end of the receiver's connections. 32314-2 Resolved a problem where logs from ic_proxy did not ROW; it sets the frame to be all rows from the partition start up through the current row's last peer (a row that ORDER BY considers equivalent to the current row, or all rows if there is no ORDER BY)

ROW; it sets the frame to be all rows from the partition start up through the current row’s last peer (a row that ORDER BY considers equivalent to the current row, or all rows if there is no ORDER BY) row; but in RANGE mode it means that the frame starts or ends with the current row’s first or last peer in the ORDER BY ordering. The value PRECEDING and value FOLLOWING cases are currently only allowed options are designed to ensure that rows that are peers in the ORDER BY ordering are treated alike; all peer rows will be in the same frame. Use either a ROWS or RANGE clause to express the bounds of the window

ROW; it sets the frame to be all rows from the partition start up through the current row's last peer (a row that ORDER BY considers equivalent to the current row, or all rows if there is no ORDER BY) row; but in RANGE mode it means that the frame starts or ends with the current row's first or last peer in the ORDER BY ordering. The value PRECEDING and value FOLLOWING cases are currently only allowed options are designed to ensure that rows that are peers in the ORDER BY ordering are treated alike; all peer rows will be in the same frame. Use either a ROWS or RANGE clause to express the bounds of the window

ROW; it sets the frame to be all rows from the partition start up through the current row's last peer (a row that ORDER BY considers equivalent to the current row, or all rows if there is no ORDER BY) row; but in RANGE mode it means that the frame starts or ends with the current row's first or last peer in the ORDER BY ordering. The value PRECEDING and value FOLLOWING cases are currently only allowed options are designed to ensure that rows that are peers in the ORDER BY ordering are treated alike; all peer rows will be in the same frame. Use either a ROWS or RANGE clause to express the bounds of the window

ROW; it sets the frame to be all rows from the partition start up through the current row's last peer (a row that ORDER BY considers equivalent to the current row, or all rows if there is no ORDER BY) row; but in RANGE mode it means that the frame starts or ends with the current row's first or last peer in the ORDER BY ordering. The value PRECEDING and value FOLLOWING cases are currently only allowed options are designed to ensure that rows that are peers in the ORDER BY ordering are treated alike; all peer rows will be in the same frame. Use either a ROWS or RANGE clause to express the bounds of the window