SQLite here is okay, but DuckDB or LevelDB would be better. Either way, no need to invent a new storage format.

otterley 4 hours ago | parent | next [-]

Neither DuckDB nor LevelDB existed when journald was created. Not to say it couldn't be done today, but just some historical context.

▲

e2le 3 hours ago | parent | prev | next [-]

Sqlite3 is present in the default installation of most Linux distributions. It has proven itself from years of battle testing in many different environments. To use DuckDB or LevelDB would probably require pulling in an additional dependency.

▲

ElectricalUnion 4 hours ago | parent | prev [-]

No duckdb (or parquet). If you want to avoid writes and write amplification, you really want to avoid re-writing all 122880 rows of a row group every time a single insert happens.

	▲	quotemstr 4 hours ago \| parent [-]
		Uh, who said anything about writing 122880 rows every time you do a single insert into DuckDB? There's a WAL. Consolidation happens in big chunks. (And it's not like journald log rotation is somehow better than WAL consolidation.) We shouldn't be making momentus choices of data format based on vague and incorrect understandings of data formats.