I run Postgres for a living and I'd say use SQLite for this. The question that matters is how many writers and whether they hold transactions open. One writer at a time, so if you do a slow thing inside a write transaction, everyone queues behind you. Things that bite: 1. Start write transactions with BEGIN IMMEDIATE. A read transaction that upgrades to a write can fail with SQLITE_BUSY straight a…