3 ms·
It's funny because to me it says pretty much the opposite: because sqlite has no server it works entirely in-process, whereas the client will be talking to post
by masklinn 4y ago
It's funny because to me it says pretty much the opposite: because sqlite has no server it works entirely in-process, whereas the client will be talking to postgres over a unix socket, or possibly a full-blown network socket.
Plus it seems to be a readonly workload, something for which posgres is not ultra relevant (not that it doesn't work, but...).