Full Joins or Full Outer Joins failing back to Legacy Planner
search cancel

Full Joins or Full Outer Joins failing back to Legacy Planner

book

Article ID: 296264

calendar_today

Updated On:

Products

VMware Tanzu Greenplum

Issue/Introduction

After upgrading to GP 4.3.21.1 or newer, queries with Full Joins or Full Outer Joins are taking longer or are failing due to "insufficient memory reserved for statement".

Environment

Product Version: 4.3

Resolution

This issue relates to Full Joins or Full Outer Joins disabled on 4.3.32.1 and higher versions using ORCA. This means that any query using Full Outer Joins with ORCA will automatically fall back to the planner.

Queries might fail with "insufficient memory reserved for statement" as the legacy planner is using more memory than the ORCA uses.

To use Full Outer Joins with ORCA
set optimizer_enable_full_join = on.