In Greenplum Database, the default GPORCA optmizer co-exists with the Postgres query
These sections describe GPORCA functionality and usage:
Overview of GPORCA
GPORCA extends the planning and optimization capabilities of the Greenplum Database Postgres optimizer.
Enabling and Disabling GPORCA
By default, Greenplum Database uses GPORCA instead of the Postgres 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. In contrast, the Postgres planner uses the statistics of each leaf partition.
Changed Behavior with the GPORCA
There are changes to Greenplum Database behavior with the GPORCA optimizer enabled (the default) as compared to the Postgres planner.
There are limitations in Greenplum Database when using the default GPORCA optimizer. GPORCA and the Postgres query optimizer currently coexist in Greenplum Database because GPORCA does not support all Greenplum Database features.