4 ms·
Faster is better than slower. Postgres is amazing. When I use Sqlite I miss many of its upsides--better data migrations and better concurrency being two. But q
by repsilat 2mo ago
Faster is better than slower.
Postgres is amazing. When I use Sqlite I miss many of its upsides--better data migrations and better concurrency being two. But queries are not free, and sometimes are slower than I'd like even with the right indexes. And for OLAP-like queries like the one in TFA you might say "well, just don't use postgres for that," but wouldn't it be better if you could? If you could use one database instead of two, or use your favourite database in more places instead of reaching for a different tool?
- a34729t 2mo agoSo why not take the approach all the fast olap systems are going and serve as the indexing and query layer and put storage at the object store level?
- repsilat 2mo agoMaybe that's the right approach, hard to say. No great harm making this kind of improvement if it isn't the globally best architectural direction.
- hmokiguess 2mo ago> wouldn't it be better if you could? If you could use one database instead of two, or use your favourite database in more places instead of reaching for a different tool? No, I used to but not anymore. I do appreciate when solving the problem is enjoyable with a tool that brings in a good experience, but I try not to get attached these days. I get what you're saying though.