SQLite prefixes its temp files with `etilqs_`

April 18, 2026
Professional woman reviewing data on laptop, working in modern office environment.
Photo by Mikhail Nilov on Pexels

The odd little prefix

Turso — a Rust rewrite of SQLite that aims for full compatibility — recently surfaced a tiny, delightful detail while implementing VACUUM: SQLite prefixes its temporary VACUUM files with etilqs_. VACUUM rebuilds a database into a fresh temporary file to reclaim space and defragment pages. The prefix is defined in the SQLite source (os.h) as the default temp-file name. Small, practical, and oddly memorable.

The origin story — and why it’s backwards

Why “etilqs_” and not “sqlite_”? The answer lives in a 2006 comment in the source. The default used to be "sqlite_", it explains, but some large third-party software (McAfee, in the note) began leaving files with that name in C:\temp. It has been reported that users, baffled by files named after the library, would Google “sqlite,” find developer contact info and call them at night. So the prefix was flipped — spelled backwards — to identify the files without inviting phone calls. Allegedly, it worked.

Small choices, big personality

It’s a good reminder that even tiny API defaults carry human consequences. A one-line macro change solved a sleep-deprivation problem and left a bit of developer folklore in the codebase. Who knew temp-file naming could be a form of reputation management? Next time you spot etilqs_ in a temp folder, you’re looking at a pragmatic hack and a story about the messy, funny ways real-world software gets used.

Sources: avi.im, Lobsters