Key things to look in Greenplum SQL Query Plans

The gadget spec URL could not be found
To find the node or operator that is consuming the most resource and taking the most time
The gadget spec URL could not be found
  1. Partition elimination
  2. Index usage
  3. Nested loop joins
  4. Check what data is being broadcast
  5. Poorly written queries / lack of statistics can lead the optimizer to ship the larger of 2 join tables significantly affecting performance
  6. Identify inflight skew
  7. Look for data spillage
The gadget spec URL could not be found


Two ways to get a plan

Explain select … from … where …;
Explain analyze select … from … where …;

The gadget spec URL could not be found
The gadget spec URL could not be found


Comments