Submission timeline
2007–2026One 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 orderThis 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…
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
- Total points
- 492
- Total comments
- 62
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2014-10-13 | Following a Select Statement Through Postgres InternalsFirst breakout | craigkerstiens | 189 | 35 |
| 2016-04-10 | Following a Select Statement Through Postgres Internals (2014)Best thread · Latest 20+ point return | rspivak | 302 | 27 |
| 2019-02-05 | Parse, Analyze, Plan and Execute – PostgreSQL Internals for SELECT | avivallssa | 1 | 0 |
