
From Code to Output: What Really Happens When You Run Python?
"Python is an interpreted language." You've probably heard this phrase countless times while...
Tag archive

"Python is an interpreted language." You've probably heard this phrase countless times while...

I recently commented on Jonathan Lewis’s blog, Savepoint Funny, where I compared how PostgreSQL...
Everything from 1.4.1 through 1.4.9 happened inside a single function, standard_planner(). Building...
A scan node sits at the leaf of the tree and pulls rows from a single table. A join node sits in the...
By the time 1.4 ends, the planner has produced one PlannedStmt. Inside it is an execution tree built...
So far we have seen the planner build candidate paths and rank them by cost, choose join methods and...
A query like SELECT region, COUNT(*) FROM sales GROUP BY region folds many rows together, collapsing...
The planner weighs how to read a table, how to join, and how to aggregate by cost, and picks the...
We opened Chapter 1 with a single line, SELECT * FROM users WHERE id = 1. For that line to leave the...
The costs in 1.4.2 and 1.4.3 were about how to read a single table. A join combines two tables, and...
In 1.5 we saw the big picture: the executor pulls results up one row at a time. That pulling...
A scan node reads rows from a table one at a time, and a join node pairs up rows arriving from its...