> If you have constant, multiple, concurrent writes on a non-append-only database, it is bound to perform poorly no matter what database you pick. This is obvi

> If you have constant, multiple, concurrent writes on a non-append-only database, it is bound to perform poorly no matter what database you pick. This is obviously incorrect, since Postgres can handle more than one simultaneous write transaction just fine. The rest of your post is accurate, but this is an intentional design decision to simplify SQLite’s implementation, not some fundamental limitation.