Pivotal Knowledge Base


Queries running on Pivotal Greenplum versions below fail with "insufficient memory reserved for statement"


  • Pivotal Greenplum (GPDB) Below
  • OS Any


In recent versions of Pivotal Greenplum (lower than 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.

  1. There was a rounding error when allocating memory to child groups of a plan when using the eager_free memory policy. This has been fixed in
  2. 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

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

Internal Comments 

See MPP-23130 and MPP-23155


Powered by Zendesk