The planner · plan reading
The join that reads one side over and over
Two small tables, and a plan that does far more work than either of them contains. Which node, and why?
The plan
plan
| node | est | actual | loops | pages | share |
|---|---|---|---|---|---|
| Nested LoopJoin Filter: (o.customer_id > c.id)Rows Removed by Filter: 1,225 | 720 | 935 | 1 | 0 | |
| → Seq Scan on c | 24 | 24 | 1 | 1 | |
| → Seq Scan on o | 90 | 90 | 24 | 24 |