rdst analyze

# Analyze an inline query
rdst analyze -q "SELECT * FROM orders WHERE customer_id = 42" --target prod-orders

# Analyze a query from the registry by hash
rdst analyze --hash a1b2c3d4e5f6 --target prod-orders

# Analyze a query from the registry by name
rdst analyze --name top-customers-by-revenue --target prod-orders

# Analyze a multi-line query from a file
rdst analyze -f ./reports/top_customers.sql --target prod-orders

# Analyze from stdin
echo "SELECT COUNT(*) FROM orders" | rdst analyze --stdin --target prod-orders

Query Analysis
════════════════════════════════════════════════════════════════
  Hash:              a1b2c3d4e5f6
  Target:            prod-orders (PostgreSQL 15.4)

  SELECT o.id, o.customer_id, o.total_cents, c.name
  FROM   orders o
  JOIN   customers c ON c.id = o.customer_id
  WHERE  o.status = 'shipped' AND o.created_at >= $1
  ORDER BY o.created_at DESC
  LIMIT  50;

Performance
  Execution time:    412.1 ms   →  SLOW (optimization needed)
  Rows examined:     2,847,201  (38.2% of orders)
  Rows returned:     50
  Scan efficiency:   INEFFICIENT
  Rating:            FAIR (65/100)

Key Issues
  • Full index scan on orders_created_at_idx; composite needed
  • Sort step: 41% of execution time
  • JOIN order picks customers first despite smaller filtered set

Index Recommendations
  1. CREATE INDEX idx_orders_status_created
       ON orders (status, created_at DESC)
       WHERE status = 'shipped';
     Expected impact: cuts scan ~90%, -300ms (~73%)

Query Rewrites
  (None suggested — rewrite candidates would not improve correctness-preserving
   performance. Fix the missing index above first.)

Readyset Cache Fit
  Candidate:        YES  (confidence: high)
  Parameter:        $1 (created_at lower bound)
  Next step:        rdst cache add a1b2c3d4e5f6 --target prod-orders-cache

rdst analyze --hash a1b2c3d4e5f6 --target prod-orders --interactive

> Why not suggest a partial index on created_at alone?
RDST: The query filters by status='shipped' first (~18% of rows), so indexing on
status, created_at lets the scan skip 82% of rows before the sort. A plain
created_at index would need to scan every shipped *and* unshipped row before
filtering.

> What if I cache this in Readyset instead?
RDST: With customer_id bound and $1 as a time cutoff, Readyset can keep the result
set warm. Cache-fit is high. You can test it with:
  rdst cache add a1b2c3d4e5f6 --target prod-orders-cache

rdst analyze --hash a1b2c3d4e5f6 --target prod-orders --review