7 ms·
When you run a relational database, you typically do it for the joins, aggregations, subqueries, etc. So a real-life scenario would include some application act
by m000 1y ago
When you run a relational database, you typically do it for the joins, aggregations, subqueries, etc. So a real-life scenario would include some application actually putting some stress on postgres.
If your don't mind overprovisioning your postgres, yes I guess the presented benchmarks are kind of representative. But they also don't add anything that you didn't know without reading the article.
- lelanthran 1y ago> If your don't mind overprovisioning your postgres Why would I mind it? I'm not using overpriced hosted PostgreSQL, after all.
- sherburt3 1y agoMy stance has always been stick to 1 database for as long as humanly possible because having 2 databases is 1000x harder.