HackerTubewatch
Surprise me
Frame from SQLite: Protégé of PostgreSQL Plays via YouTube's privacy-enhanced embed

SQLite: Protégé of PostgreSQL

Andrea Ross
Talks
YouTube
1 HN user recommended this talk1 month2014–2017 score 1
Years with an HN recommendation, 2007–2026

Recommended as a talk from SQLite's main author, and cited for the project's focus on backwards compatibility and for deployment anecdotes.

D. Richard Hipp's PGCon 2014 keynote on SQLite's relationship to PostgreSQL. He explains that SQLite was originally written from PostgreSQL 6.5 documentation and that the two engines serve different classes of problems.

“You might also enjoy this talk by the main author of SQLite” (HN, 2017)

1 recommendations · 2 citations · Talks · intermediate

3 Hacker News comments

From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.

@felixge Aug 2017 Recommends
on HN thread How Postgres Makes Transactions Atomic
AFAIK SQLite doesn't achieve atomicity by virtue of its global write lock. It does so by using a rollback journal (default) or WAL. So it's not really all that different from PostgreSQL in that regard and the authors point remains valid :). You might also enjoy this talk by the main author of SQLite: [this video] (SQLite: Protégé of PostgreSQL)
Talk by SQLite's main author comparing it to PostgreSQL.

Citations, criticism and jokes

@keeperofdakeys Jul 2014 Cites it
on HN thread SQLite: Small, Fast, Reliable – Choose any three
As a read-only database, sqlite doesn't have too many limits, since the storage mechanism is flexible enough to allow fast queries. The problem comes when you start writing, and reads have to wait for them. Also, (I believe) it was this talk [this video] that mentions sqlite being used in adobe lightroom, and it being faster to access thumbnails from an sqlite database.
Talk mentions SQLite use in Adobe Lightroom for thumbnails.
@justinclift Feb 2017 Cites it
on HN thread Ask HN: Is sqlite good for long-term persistence?
Not sure about a 30 year timeframe. 10 years seems like it wouldn't be any kind of problem (personal opinion), but 30 years is an awful long time. That being said, the SQLite development Community are very very big on backwards compatibility. eg: [this video] Hmmmm, there's a better talk by D. Richard Hipp around, but I'm not finding it atm. In the better talk he explains they (SQLite) are planning to be around for the 30 year timeframe you mention. Something to do with an airplane manufacturer looking for long term guarantees, but I don't remember the details.
Example of SQLite community's focus on backwards compatibility.

Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.

Keyboard shortcuts

/
Search
j k
Next / previous video
r
Surprise me
l
Like (video page)
w
Watch later (video page)
?
This help
Esc
Close