Top all-time · #4020
Jeremy Schneider
Personal blog · ardentperf.comdatasystemsprogramming
Jeremy Schneider writes Ardent Performance Computing, a personal blog at ardentperf.com about data, systems and programming. Since 2021, 19 different Hacker News readers have linked it 30 times, most often “UUID Benchmark War”. It is still writing: the last post was on 2026-10-21, and you can follow it by feed.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
Jeremy Schneider's Postgres posts on UUID vs bigint primary keys, benchmarks and replication/upgrade approaches. HN readers link them for detailed technical explanations of Postgres internals.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Jeremy Schneider
Most-linked posts?
- UUID Benchmark War3 people · 3 mentions · first linked 2024-02-04
- PostgreSQL Performance Puzzle2 people · 2 mentions · first linked 2022-07-17
- Postgres Indexes, Partitioning and LWLock:LockManager Scalability2 people · 2 mentions · first linked 2024-03-04
- A Hairy PostgreSQL Incident2 people · 2 mentions · first linked 2022-02-10
- PostgreSQL Logical Replicas and Snapshots: Proceed Carefully2 people · 2 mentions · first linked 2022-02-17
- Paranoid SQL Execution on Postgres2 people · 2 mentions · first linked 2021-07-07
What Hacker News says?
Another interesting article from Feb-2024 [0] where the cost of inserting a uuid7() and a bigint is basically the same. To me it wasn't quite clear what the problem with the buffer cache is but the author makes it much more clear than OP's article: > We need to read blocks from the disk when they are not in the PostgreSQL buffer cache. Conveniently, PostgreSQL makes it very easy to inspect the contents of the buffer…
Comment linking /2024/02/03/uuid-benchmark-war
on “Avoid UUID Version 4 Primary Keys in Postgres”Submitted A Hairy PostgreSQL Incident as a story · 155 points
HN discussionContrary to intuition, bigint ends up only 25% smaller on disk than UUIDv7 and no improvement in speed. Honestly in 2024, 32-bit ints are generally a poor fit. Either the table is small enough to be considered a lookup table (16-bit int) or could grow to unknown bounds given enough time (64-bit int). Sequential ids are guessable (which could be a security issue), cannot be generated on the client, and can hinder sha…
Comment linking /2024/02/03/uuid-benchmark-war/
on “Why does everyone run ancient Postgres versions?”Submitted UUID Benchmark War as a story · 133 points
HN discussionRelated on the front page, "UUID Benchmark War": * https://ardentperf.com/2024/02/03/uuid-benchmark-war/ * https://news.ycombinator.com/item?id=39254871
Comment linking /2024/02/03/uuid-benchmark-war/
on “UUID v7”Submitted Paranoid SQL Execution on Postgres as a story · 97 points
HN discussionIndeed - People In The Know have some cocnerns with this approach: https://ardentperf.com/2021/07/26/postgresql-logical-replica... . At $work we did use this approach to upgrade a large, high throughput PG database, but to mitigate the risk we did a full checksum of the tables. This worked something like: * Set up logical replica, via 'instacart' approach * Attach physical replicas to the primary instance and the lo…
Comment linking /2021/07/26/postgresql-logical-replicas-and-snapshots-proceed-carefully/
on “Zero Downtime Postgres Upgrades”Submitted Postgres recovery_prefetch can cause outages as a story · 45 points
HN discussionSubmitted Understanding CPU on AIX Power SMT Systems as a story · 43 points
HN discussionSubmitted Major Developments in Postgres Extension Discovery and Distribution as a story · 26 points
HN discussionSubmitted A Hairy PostgreSQL Incident as a story · 12 points
HN discussionSubmitted Sanitized SQL as a story · 4 points
HN discussionSubmitted PostgreSQL Happiness Hints (2022) as a story · 4 points
HN discussionSubmitted Challenges of Postgres Containers as a story · 3 points
HN discussionSubmitted PostgreSQL Logical Replicas and Snapshots: Proceed Carefully as a story · 3 points
HN discussionSubmitted The Scott Shambaugh Situation Clarifies How Dumb We Are Acting as a story · 2 points
HN discussionSubmitted Postgres IPC:SyncRep – Sync Replication Is Not Actually Sync Replication as a story · 2 points
HN discussionSubmitted Default Sort Order in Db2, SQL Server, Oracle and Postgres 17 as a story · 2 points
HN discussionSubmitted Did Postgres Lose My Data? as a story · 2 points
HN discussionSubmitted PostgreSQL Performance Puzzle as a story · 2 points
HN discussionSubmitted PostgreSQL Performance Puzzle as a story · 2 points
HN discussionSubmitted Paranoid SQL Execution on Postgres as a story · 2 points
HN discussionSubmitted Zero Autovacuum_cost_delay, Write Storms, and You as a story · 1 points
HN discussionSubmitted Database Schema Migrations in 2026 – Survey as a story · 1 points
HN discussionSubmitted Postgres Indexes, Partitioning and LWLock:LockManager Scalability as a story · 1 points
HN discussionSubmitted Blocking-Lock Brownouts Can Escalate from Row-Level to Complete System Outages as a story · 1 points
HN discussionSubmitted Run Jepsen against CloudNativePG to see sync replication prevent data loss as a story · 1 points
HN discussionSubmitted Default Sort Order in Db2, SQL Server, Oracle and Postgres 17 as a story · 1 points
HN discussionSubmitted Postgres Indexes, Partitioning and LWLock:LockManager Scalability as a story · 1 points
HN discussionSubmitted Researching the Performance Puzzle as a story · 1 points
HN discussion
