Run a query and this tab will break down the
time it spent planning versus executing, the
volume of data it read, and the number of
rows it returned.
Reach for it when a query is slower than you
expect: the split between planning and
execution tells you whether the cost is in
working out the answer or in reading the
data to answer it.
How did Opteryx answer that?
Run a query and this tab will show the steps
the engine took — reads, filters,
joins and aggregations — as a tree,
with the rows and time each step accounted
for.
Each step feeds the one it is nested under,
so the deepest steps run first. The step
handling the most rows is usually the one
worth attacking, and a filter that sits
close to the read it belongs to is far
cheaper than the same filter applied after a
join.
Chart type
Y axis
Run a query that returns at least one
numeric column, then choose what to plot
on each axis using the controls to the
left. Charts can be saved as an image
with Download PNG.