Static Plan Checker in GPCC Shows Only First Line of Plan
Article ID: 409636
Updated On:
Products
Issue/Introduction
Users observed that when they generate an EXPLAIN plan from DBeaver Community and paste it into GPCC Static Plan Checker, only the first line of the plan is displayed, the full plan is not visible.
However, when the same plan is generated from the CLI (psql) or when an extra space is added in the second line of the plan text, GPCC successfully shows the complete plan.
Environment
GPCC - 6.X & 7.3.1
Cause
The issue is due to differences in indent formatting between EXPLAIN plans generated by DBeaver and those generated via the CLI (psql):
-
DBeaver output uses two-space indents at the beginning of nested plan lines.
-
CLI output uses three-space indents at the beginning of nested plan lines.
GPCC’s Static Plan Checker interprets the two-space indent format (from DBeaver) as a SubPlan, which causes it to truncate and display only the first line of the plan.
This is why adding an extra space (or using CLI output) resolves the issue.
Resolution
Workaround:
- Copy execution plans directly from the CLI (psql) instead of DBeaver when uploading to GPCC Static Plan Checker.
- Alternatively, manually adjust indentation (e.g., add one space at the beginning of each indented line) before submission.
Permanent Fix:
- A patch is planned for a future GPCC release to ensure GPCC correctly interprets both two-space and three-space indented EXPLAIN formats.
Feedback
