HN Hall of Fame Weekly email

Following a Select Statement Through Postgres Internals (2014)

patshaughnessy.net Books & learning Tutorials & guides Software engineering Candidate
Screenshot of patshaughnessy.net captured 2026-07-20
Page preview · captured 2026-07-20

Resurfaced independently across 3 calendar years, with breakout response in 2 of them.

submissions
3
submitters
3
observed span
2014–2019
peak thread · 35 comments
302 pts
latest 20+ return · 2016-04-10
302 pts

Submission timeline

2007–2026

One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.

First comments on top threads

HN comment order

This article was also discussed before: https://news.ycombinator.com/item?id=8449329 Pat Shaughnessy has 3 other similar articles about Postgres internals. He does a great job of combining high level explanations, visual aids, and gritty details. Discovering the Computer Science Behind Postgres Indexes http://patshaughnessy.net/2014/11/11/discovering-the-compute... A Look at How Postgres Executes a Tiny Join http://patshaughnessy.net/2015/11/24/a-look-at-how-postgres-... Is Your Postgres Query Starved for Memory?…

I liked the article, and I know this is nitpicking, but I disagree that creating an index is the best solution for eliminating the sequential scan. Hopefully the next article mentions it. Just drop sort clause. Returning the user with the lowest id seems like an unusual use case. Imagine searching for a name in a phone book and only finding the oldest person with that name, or the person with the lowest phone number. More common cases are checking…

tofflos·189-point thread·

The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.

Breakout years
2

100+ points or 50+ comments

Total points
492

reference only — not used in Hall rules or ranking

Total comments
62

reference only — not used in Hall rules or ranking

Every submission

DateTitle as submittedByPointsComments
2014-10-13Following a Select Statement Through Postgres InternalsFirst breakoutcraigkerstiens18935
2016-04-10Following a Select Statement Through Postgres Internals (2014)Best thread · Latest 20+ point returnrspivak30227
2019-02-05Parse, Analyze, Plan and Execute – PostgreSQL Internals for SELECTavivallssa10