A newer version of this documentation is available. Use the version menu above to view the most up-to-date release of the Greenplum 5.x documentation.
In Greenplum Database, the default GPORCA optmizer co-exists with the legacy query
These sections describe GPORCA functionality and usage:
Overview of GPORCA
GPORCA extends the planning and optimization capabilities of the Greenplum Database legacy optimizer.
Enabling and Disabling GPORCA
By default, Greenplum Database uses GPORCA instead of the legacy query planner. Server configuration parameters enable or disable GPORCA.
Collecting Root Partition Statistics
For a partitioned table, GPORCA uses statistics of the table root partition to generate query plans. These statistics are used for determining the join order, for splitting and joining aggregate nodes, and for costing the query steps. This is in contrast to the legacy planner, which uses the statistics of each leaf partition. If you execute queries on partitioned tables, you must collect statistics on the root partition and periodically update those statistics to ensure that GPORCA can generate optimal query plans.
Changed Behavior with the GPORCA
There are changes to Greenplum Database behavior with the GPORCA optimizer enabled (the default) as compared to the legacy planner.
There are limitations in Greenplum Database when using the default GPORCA optimizer. GPORCA and the legacy query optimizer currently coexist in Greenplum Database because GPORCA does not support all Greenplum Database features.