|Pivotal Greenplum (GPDB)||Below 184.108.40.206|
In recent versions of Pivotal Greenplum (lower than 220.127.116.11) many queries that used to be running successfully previously are now failing and require more memory to run successfully.
Specifically, these queries are failing with the error:
"insufficient memory reserved for statement"
There were two bugs identified in the earlier 4.3 GPDB releases.
- There was a rounding error when allocating memory to child groups of a plan when using the
eager_freememory policy. This has been fixed in 18.104.22.168.
- We would fail to account for some of the memory that has already been allocated in a plan, resulting in over-allocating memory when using
eager_free. This has been fixed in 22.214.171.124.
In this case of shortcomings with memory, accounting has been addressed and the full cost for the query is now being enforced.
Upgrade to a recent software release (higher than 126.96.36.199).
See MPP-23130 and MPP-23155