If you mean postgres without custom configuration, absolutely. But postgres can run entirely in memory via mmap just like LMDB does.

Nonetheless I find it too heavyweight to configure and manage whereas LMDB is just compiled in, doesn't need the multiple-client stuff, the SQL parsing, the query planner, etc... if you code that stuff into your client, which can be done when the queries are not too numerous or complex.

So yeah I like LMDB better for this use case, but my brother the postgres core dev insists postgres can do key-value, nosql, all-in-memory, etc, just as good as the other databses.  I say "there there little brother, I'm sure it's real good."