NexQLv2.4.0

Analyze

From slow query to concrete fix

Run EXPLAIN ANALYZE in a notebook cell to open an interactive plan tree, a flame graph, and a diff between runs. Index recommendations are based on your schema.

Pro, Sponsor

A plan with a sequential scan, and the same query after adding an index.

How you use it

  1. Run EXPLAIN from a notebook cell

    The Explain Analyze CodeLens appends a plan cell. Read the text plan for a quick scan, or the Visual tab for structure.

    EXPLAIN (ANALYZE, BUFFERS)
SELECT * FROM orders
WHERE created_at >= NOW() - INTERVAL '30 days';
  2. Open Plan Studio on the result

    The tree and flame graph highlight sequential scans and nested loops. Compare two runs side by side.

  3. Ask AI to optimize with schema context

    The Optimize CodeLens or the assistant suggests an index, with the expected impact.

    CREATE INDEX CONCURRENTLY idx_orders_created_at
  ON orders (created_at DESC);
  4. Chart a result set

    Draw bar, line or pie charts from query output. The Analyst tab adds pivot and histogram, with an optional Send to Assistant.

Key facts

  • Plan: Pro, Sponsor
  • Visual EXPLAIN
  • Plan diff between runs
  • Flame graph
  • Index suggestions
  • Charts and an Analyst tab on result sets
SQL notebooksMix SQL cells and markdown in a .pgsql file, run them, and keep the file in git.SQL assistantAsk in plain English. The assistant grounds on your live schema and never runs SQL for you.Live dashboardConnections, locks, cache hit ratio and top tables, read from pg_stat views.